Mapping issue for choice field in Form layout

[VullankiL]

Hi All,

In my custom application, there is one field called "include_custom_data" (choices - Yes, No, None) created in a table like "custom_requested_item_aux".  
And there is another table called "custom_requested_item". Both tables have reference to each other.

I have added the "include_custom_data" field in the form layout of "custom_requested_item" table in one section using dot-walking through "req_item_aux" field. 

I am mapping these field value using record producer variable called "include_custom_data_var". ( choices - Yes, No, None). For both dictionary entry of the field, and record producer variable, the back-end values of choices are same. 
The values are getting mapped correctly and showing correctly for the same record, if I open it in the "custom_requested_item_aux" table record. The value is correctly mapping and can update manually to any of three choices (all are visible). It is working fine.

However, the issue is the choice values are not showing for this field in the Form layout of "custom_requested_item" record, where I have added this field in one section. There is no duplicate fields, and back-end values of choices are same.. working in AUX record, but not in "custom_requested_item" record even after both are same.  Also, the mapped values showing as back-end values in "blue color" in form layout not in black color..

Please suggest some solution to this..

Thank you,

[Ankur Bawiskar]

@VullankiL 

both the fields on form are dot walked and will derive their value from the Referenced record present in reference field.

you are trying to set values to them directly and hence it's showing in blue color

Example: If you have incident as reference field on problem form and added Incident->Caller ID as dot walked field on problem form, then you need to set INC value in that reference field so that Caller is auto populated as dot walked.

Simply setting caller field on form which is dot walked won't work

You need to set the reference field as well for this.

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[VullankiL]

Hi @Ankur Bawiskar ,

For both the tables "custom_requested_item_aux" and "custom_requested_item", the 2-way reference fields are there, to reference to one another and vice-versa. 
I have added other dot-walked fields also like this from same table ""custom_requested_item_aux" to the "custom_requested_item" form layout.. for all remaining fields it is working.
Only for this field it is happening, the back-end fields values are are matching exactly..
Can't able to identify why it is happening.. Any solution for this?

Thank you

[kaushal_snow]

@VullankiL ,

This typically happens because the field that you’re dot walking to is not actually stored on the target record, so your form layout is rendering the reference path as a link (hence the blue value) instead of showing the choice list inline; what you’ll want to do is either copy/mirror the value from the auxiliary table into a real field on the main table (via a business rule or script) or make sure the choice field on the aux table is truly inherited/duplicated in the main table rather than just being referenced, and verify that the ACL and form dictionary settings are correct so the choice list can render in the form for the dot walked field....

If you found my response helpful, please mark it as ‘Accept as Solution’ and ‘Helpful’. This helps other community members find the right answer more easily and supports the community.