I've got a bit of an odd setup, will try to briefly explain:
I've got a view which lists 'vehicles' (table - using flipped table so vehicles are columns) .. within that I have a field of 'Jobs' (one row), which is actually another view (using Views Field View) called 'Jobs' which uses contextual arguments (ie: the vehicle) to list only jobs that apply to the vehicle (column).
This all works well, I'd tried to implement passing exposed filters from the parent view to the 'child' views, however gave up on this and just implemented some javascript which achieves the same thing.
Now, the issue. Each 'job' has a 'status' field, this is the editable field. When there's only a few (ie, upto 3 or so) jobs listed on the page, the editable field works fine, status is updated etc.
When there is more than a few (and under testing there's been up to 30), only the first few editable fields will actually work. Trying to update any other editable fields will throw:
An AJAX HTTP error occurred.
HTTP Result Code: 500
Debugging information follows.
Path: /system/ajax
StatusText: Service unavailable (with message)
ResponseText: EntityMalformedException: Missing bundle property on entity of type node. in entity_extract_ids() (line 7501 of /home/poc/public_html/includes/common.inc).
As a work around I can just filter the results down so there are never more than a few jobs listed, however this isn't a viable solution.
If interested you can reproduce the error on this live site:
http://poc.purplec.com.au/dispatch-log?date%5Bvalue%5D%5Byear%5D=2012&da...
User: dotest
Pass: test123
The above authenticated user has access to edit nodes etc. Please use the above link .. You'll find the error will always occur when trying to edit the field in the 4th column, the first 3 will work. This always occurs .. you can try filtering by other dates where different amount of jobs come up however the issue is always the same, the first few editable fields are fine, the rest throw an error.
Any feedback on this issue would be greatly appreciated, or even suggestions on a better way to implement this as I'm thinking the 'views within views' approach may be (one of) the cause of my woes. I'm open to any suggestions on how to build this as its more of a 'proof of concept' / 'test development' project. Display Suite has been mentioned, but I'm not hugely familiar with it.