Expand my Community achievements bar.

Enhance your AEM Assets & Boost Your Development: [AEM Gems | June 19, 2024] Improving the Developer Experience with New APIs and Events
SOLVED

Exclusion group values not exporting to "Merge Data" spreadsheet

Avatar

Level 4

Hi everyone,

I've noticed that most of my radio button values do not show up on the spreadsheet (yet some inexplicably do).  Has anyone else ran into this problem?

1 Accepted Solution

Avatar

Correct answer by
Level 4

For anyone else struggling with this, here's how I went wrong:

I named the individual radio buttons on the hierarchy pallete. For reasons unknown to me, they MUST be left as "(untitled radio button)" .  I had designated names such as "yes", "no", and some multiple choice answers.   RawValues only export for these if they are left with their default unititled names.  The exclusion group itself can be renamed of course-that seems to have no effect on the issue.

Just an example of some baffling programming in LiveCycle.

View solution in original post

4 Replies

Avatar

Level 7

It could be to do with binding. Some of the options don't export. I know 'Use name' definately does export so that's a safe option.

Avatar

Level 4

I do specify item values (1 for Yes, 2 for No) and the Data Binding is "Use name (ERMyesno)"

The radio button list name is ERMyesno.

Avatar

Correct answer by
Level 4

For anyone else struggling with this, here's how I went wrong:

I named the individual radio buttons on the hierarchy pallete. For reasons unknown to me, they MUST be left as "(untitled radio button)" .  I had designated names such as "yes", "no", and some multiple choice answers.   RawValues only export for these if they are left with their default unititled names.  The exclusion group itself can be renamed of course-that seems to have no effect on the issue.

Just an example of some baffling programming in LiveCycle.

Avatar

Former Community Member

Many thanks for this workaround.  I have been searching for a solution for 18 months!!  It would be good for Adobe to fix this glitch in the Acrobat X program.  

I have also gone one step further and named the exclusion group with codes to identify what the values refer to.  (eg. The name of one exclusion group with three options is SSPtype-edbd1-intell2-hosp5)  This wouldn't be practical for long lists of options but it helps when it comes time to interpreting the exported data.

I wonder if there are any other field types that have weird problems like this one????

Once again, many thanks for your assistance!!!

jeannie