LightningFlowComponents
LightningFlowComponents copied to clipboard
alexed1
Quick Choice static list code calling incorrect attribute
@fromsteinsfdc This report came in: Filip replied in unofficialsf I've started to receive some weird error in flow builder on currently added Quick Choice components: Error during LWC component connect phase: [Unknown public property "availableFieldTypes" of element <c-fsc_pick-object-and-field>. This is likely a typo on the corresponding attribute "available-field-types".] When I'm adding a new one everything is fine. Any ideas what can be an issue here ?
looking at the code, fsc_pick-object-and-field does not have an availableFieldTypes input attribute. It does have an availableFields attribute.
it looks like code you added for static choices is passing the incorrect attribute here:
https://github.com/alexed1/LightningFlowComponents/blame/master/flow_screen_components/FlowScreenComponentsBasePack/force-app/main/default/lwc/fsc_quickChoiceCpe/fsc_quickChoiceCpe.html
Can you investigate?
@alexed1 Huh. I have no memory of modifying that line, my static choices portion didn't touch or interact with that part of the code at all (by definition)... I haven't gotten a chance to do any testing yet today, but it should be as simple as correcting that attribute to the correct availableFields unless I'm missing something?
I haven't had time to go deeper...hopefully you're right. alex
Alex Edelstein VP Product Management - Automation, Orchestration and Decisioning Salesforce
https://smart.salesforce.com/sig/aedelstein//us_mb/default/link.html
On Mon, Aug 16, 2021 at 3:00 PM fromsteinsfdc @.***> wrote:
@alexed1 https://github.com/alexed1 Huh. I have no memory of modifying that line, my static choices portion didn't touch or interact with that part of the code at all (by definition)... I haven't gotten a chance to do any testing yet today, but it should be as simple as correcting that attribute to the correct availableFields unless I'm missing something?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/alexed1/LightningFlowComponents/issues/869#issuecomment-899845482, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAX62E7QXZQSYWDCBC3M2ODT5GC7ZANCNFSM5CH5OIGA .
@alexed1 I installed the latest basepack versions and did not get an error message, though it does prevent the object picker component from successfully displaying only picklist fields. Then I re-read Filip's report and he's saying it only occurs on existing quickChoice components, which I don't think I'm able to test cause I don't have any orgs use it. Should I just correct the attribute and submit a PR?
@alexed1 I installed the latest basepack versions and did not get an error message, though it does prevent the object picker component from successfully displaying only picklist fields. Then I re-read Filip's report and he's saying it only occurs on existing quickChoice components, which I don't think I'm able to test cause I don't have any orgs use it. Should I just correct the attribute and submit a PR?
This is happening in an org for me on new quickChoice components using component ver 2.35. Any update on a fix?
@eclarke12 Are you still experiencing this? I have installed this on several orgs and have not gotten any errors.
@eclarke12 Are you still experiencing this? I have installed this on several orgs and have not gotten any errors.
@AndyHaas I switched jobs since my post and I'm not working in Flows lately, so I haven't used the component.