Filed Collection issue

I have the same issue as well.

I actually had a brief look and from what I can see, this is occurring due to the preview() method within the views_plugin_display_services.inc:

function preview() {
    module_load_include('resource.inc', 'services_views');
    return '<pre>' . var_export(services_views_execute_view(NULL, $this->view, $this->display->id), TRUE) . '</pre>';
  }

As a test, changing the:

return '<pre>' . var_export(services_views_execute_view(NULL, $this->view, $this->display->id), TRUE) . '</pre>';

to:
return json_encode(services_views_execute_view(NULL, $this->view, $this->display->id));

did display the JSON version however:

• Characters were being escaped.
• This may have impact on when previewing the view.

Can someone explain how the preview() method is called or which hook it is used and what would be a better way to return the JSON/XML representation of the field collection? I'm quite new at Drupal development...

Anyone know how to make this spit out valid xml of the content?

This is my attempt at supporting field collections. What this will do is add a View Mode to your field collections called 'Services' that allows you to define data values for your entity to be embedded into the view.

1. In the display of your field collections, enable the Services view mode
2. Set the fields to the "Services Raw" formatter
3. Each field has some settings. Text and taxonomy reference have a few extra.
4. There is also an alter hook you can use to further manipulate the data: hook_services_field_collection_data_alter($field_data, $entity, $field_name)
5. In the View, add your field collection item as a field, select Fields Only as the formatter and Services as the mode.

In more detail, this patch fixes the Services Raw formatter for entity field displays, adds a custom view mode, adds extra settings to the entity field formatter and processes field collections in the view as separate entities.

#4 Works Fine, but after patching services views, we got many Undefined index warnings like this:

Notice: Undefined variable: element_key in services_views_execute_view() (line 171 of /sites/all/modules/services_views/services_views.resource.inc).
Notice: Undefined index: text_processing in _text_sanitize() (line 319 of /modules/field/modules/text/text.module).
Notice: Undefined index: text_processing in _text_sanitize() (line 319 of /modules/field/modules/text/text.module).
Notice: Undefined index: services in services_views_execute_view() (line 168 of /sites/all/modules/services_views/services_views.resource.inc).
Notice: Undefined index: services in services_views_execute_view() (line 168 of /sites/all/modules/services_views/services_views.resource.inc).
Notice: Undefined index: services in services_views_execute_view() (line 168 of /sites/all/modules/services_views/services_views.resource.inc).

Any Idea how to fix this?

Thanks for the report, @Andiff.

I didn't see those on my install. It looks like it is expecting the "services" view mode and not finding it. Have you tried clearing Drupal's cache?

I'll try to reproduce it on my end today. Any other information you can provide about your setup and the steps you took are greatly appreciated and can help speed things up.

The patch on #4 is for 7.x-1.0-beta2 or -dev?

Patches should always be rolled against -dev branches so maintainers can (hopefully) apply them to their most up-to-date codebase.

If you use the latest dev release of Services Views, the patch will fail for the last hunk: services_views.resource.inc. This is due to the change in code for beta4. Tried to look for beta3 but from the releases, I could only see beta 2! It is fairly simple to manually implement the rejected patch.

I followed the steps in #4. One thing I found out is that the "Skip empty values" setting will still skip empty values even if you un-selected the checkbox.

Applied the patch in #4 to beta2, followed the procedure proveded by KeyboardCowboy and it works.

Updated to recently released services views 1.0, applied the patch manually and it works.

Solving this problem in any other way is very difficult, this patch is a huge timesaver. Thanks KeyboardCowboy!

I'm getting many notices from this (first) line in the patch:

$element_key = $instance['display']['services']['settings']['data_element_key'];
$element_key = ($element_key ? $element_key : $instance['label']);

Notice: Undefined index: data_element_key i services_views_execute_view() etc. etc.

There is nothing being broken since the second line above checks $element_key. It seems that this part of the code handles the case where you specify the value key in the services view mode. What's weird is that my custom keys show up just fine, so I guess I'm wrong in my thinking somewhere.

First of all, thank you KeyboardCowboy for your help on this! :)

This works great however I now have a curious problem. For my field collection, I have an image field that previously was only set to only one image. Now, due to changes in requirements, I need to have multiple images for this image field.

I've set the field to have multiple images and have put in test images, however when I ran my service, only last image added in is being returned.

Is there a way to allow multiple images to be returned?

Thank you!

Hi !
That works perfectly ! Thanks a lot. This is really a must-have in Services Views module.

PS: just a very little change to get it work with current 1.x version attached.

sadly i can't re-open this but it shouldn't be closed until committed somewhere.. which i don't think it is.