You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Mapping fields for top level response works as expected
Added a nested field map for a response array, but the field value list displays fields from the parent table, not the child table...
Steps to reproduce
create a new request whose response will contain a nested array
create a new field map
select a field and table to map the parent fields
click Nested Array in the list of response fields, to create a field map
select file and table to map the parent fields
go back and work with the parent fields
choose the child field map
try to map fields
Expected result:
Field value list displays field names from child table
Actual result:
Field value list displays field names from parent table
...I got it to work by reselecting the table for the nested field map:
Choose table
Refresh file list and select
Refresh the table list and select
In conclusion, it is possible to operate Generator 2.0.6 in an way which does not offer the correct value list contents for a nested field map. I suspect it's a missing refresh when navigating back and forth between the two maps
The text was updated successfully, but these errors were encountered:
Just downloaded 2.0.6, testing on FMPA 16.0.3 Mac
Mapping fields for top level response works as expected
Added a nested field map for a response array, but the field value list displays fields from the parent table, not the child table...
Steps to reproduce
Expected result:
Field value list displays field names from child table
Actual result:
Field value list displays field names from parent table
...I got it to work by reselecting the table for the nested field map:
In conclusion, it is possible to operate Generator 2.0.6 in an way which does not offer the correct value list contents for a nested field map. I suspect it's a missing refresh when navigating back and forth between the two maps
The text was updated successfully, but these errors were encountered: