alexed1
*DataTable Configuration Wizard* - _({!apexColSelectedFieldDescriptors_usf})_ - Data Type of the resource you entered isn't compatible
Steps to reproduce
Steps to reproduce the behavior:
- Deploy the source code to an org (no modification to the code other than fixing some namespacing. Not installed package.
- Load the 'Configuration wizard flow'
- Observe the 'The data type of the resource you entered isn't compatible.' error for the '{!apexColSelectedFieldDescriptors_usf}' value in the 'selectedOptionsFieldDescriptorList' output variable of the dual list box component on 'select fields' screen.
- See error
Deleting the dual list box component from the flow completely allows for no errors and the flow can be run but then this result in unhandled faults. Trying to understand what could be the problem with the apex defined variable that is only observable in the scenario of no namespacing/deployed source to an org.
Screenshots
Paste the output of the logs here.
The documentation outlines all of the components from the BasePacks that are used by the Datatable component including 3 Apex Defined data types that are part of the FlowActionsBasePack. You will need to include those and modify all references to them that include the base pack namespace.
- The following components from the Flow Base Packs are used in Datatable: FlowActionsBasePack usf.FieldDescriptor usf.FieldPickerController usf.GetFieldInformation
FlowScreenComponentsBasePack CustomLabels.labels fsc_displayError fsc_flowBanner fsc_flowCheckbox fsc_flowCombobox fsc_flowComboboxUtils fsc_pickIcon fsc_pickObjectAndField fsc_pickObjectAndFieldUtils fsc_screenFlow fsc_screenFlow.page fsc_screenFlowApp.app fsc_searchableDataTable
I think I've narrowed it down and wondering if this bug also exists even in the managed package form as namespacing doesn't seem to have anything to do with it.
The output value of selectedOptionsFieldDescriptorList does not seem to allow mapping to a apex collection variable strangely. As it's trying to map to {!apexColSelectedFieldDescriptors_usf} which is an apex defined variable for the fieldDescriptor class allowing multiple.
Perhaps this is actually an issue with Dual Lst Box v3 rather than Datatable.
It looks like Dual List Box 3 is looking for usf3.FieldDescriptor
The datatable uses a serialized string. This post will give you more info. https://unofficialsf.com/working-with-serialized-data/
On Wed, Apr 5, 2023 at 11:26 AM Jack McGrady @.***> wrote:
I think I've narrowed it down and wondering if this bug also exists even in the managed package form as namespacing doesn't seem to have anything to do with it.
The output value of selectedOptionsFieldDescriptorList does not seem to allow mapping to a apex collection variable strangely. As it's trying to map to {!apexColSelectedFieldDescriptors_usf} which is an apex defined variable for the fieldDescriptor class allowing multiple.
[image: image] https://user-images.githubusercontent.com/64766455/230128534-b4d5b5c9-d282-4aef-8573-f632d60670ca.png
Perhaps this is actually an issue with Dual Lst Box v3 rather than Datatable.
— Reply to this email directly, view it on GitHub https://github.com/alexed1/LightningFlowComponents/issues/1382#issuecomment-1497680767, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF4UHX5IC3IPJK5M6FRCKKTW7WFJ7ANCNFSM6AAAAAAWRW6D2I . You are receiving this because you commented.Message ID: @.***>
I removed all usf3. references to clear out any of the namespacing so all references still appear correct minus the usf3.prefix Wondering if there is some other reference or use of this I haven't identified but the repo looks clean of them now.
The errors seems like it's indicating two different classes are mentioned in the input vs the output but that doesn't appear to be the case from what I see.
This article might apply to how the FlowTableViewDefinition object is configured. https://docs.google.com/document/d/1rqOREveltPp9sVPkEopt7N1ZPGvLC2ZTDzPzpVYms68/edit
On Wed, Apr 5, 2023 at 12:23 PM Jack McGrady @.***> wrote:
I removed all usf3. references to clear out any of the namespacing so all references still appear correct minus the usf3.prefix Wondering if there is some other reference or use of this I haven't identified but the repo looks clean of them now.
The errors seems like it's indicating two different classes are mentioned in the input vs the output but that doesn't appear to be the case from what I see.
— Reply to this email directly, view it on GitHub https://github.com/alexed1/LightningFlowComponents/issues/1382#issuecomment-1497778307, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF4UHXZJH2YSLDI4FVEJEBTW7WL7VANCNFSM6AAAAAAWRW6D2I . You are receiving this because you commented.Message ID: @.***>