Hi,

following issue:

  1. Custrom PHP Code field: I want to run some PHP in order to get a result into a field. This custom PHP code seems not to run - the field stays mostly empty.
  2. Excluded from display: I want some fields to be included into other fields. I tried this as usual by excluding them from display and include them into this field by rewriting the output of the field and inserting the excluded field by its replacement pattern. But this leads to strange result - not the value from the excluded field is shown but always the same number or nothing.

Anyone knows about this behavior in exports of views?

Greez,
Tobias

Comments

tobiberlin’s picture

tobiberlin
Primary language German
Location Berlin, Germany
commented
Title: Custom PHP field and fields excluded from display and included by replacement pattern not showing right in csv export » Fields excluded from display and included by replacement pattern not showing right in csv export

ok... regarding PHP code there was a mistake in my code... sorry for that... but still the issue with the excluded fields appears

gabrielu’s picture

gabrielu commented

This happens here too. Whenever you try to export as CSV and exclude one field from display and replace into another field using replacement patterns, it will always show the first result.
I am having something like
- First name - excluded
- Last name - exlcuded
- Custom text - replace: [value_1] [value_2]
And all users are exported like `Bill Joe` (first result values)

jzornig’s picture

jzornig commented

I'm experiencing the same issue. I can't get customfields to appear in the csv output and fields that I exclude are displayed.

carl@west-tec.com’s picture

carl@west-tec.com commented
Priority: Normal » Major

I'm experiencing the same issue. Although the custom field created by replacement patern is show correct in the preview of the view, it is not in the csv-output. The field formatted correctly, but the replacement values of the first row are repeated in every row.

A few hours later.... I noticed that the export is OK in XLS if you add the fields you use in the replacement pattern also in the result.

jromine’s picture

jromine commented

I think the excluded fields issue is fixed by the patch in http://drupal.org/node/1142196#comment-4915880

travist’s picture

travist commented
Status: Active » Closed (duplicate)

Duplicate of #1142196: Using tokens from other fields that are excluded from the view is broken.