search

alexed1 / LightningFlowComponents

A collection of unofficial Flow extensions that can be used to enhance Salesforce Flow and Orchestrator.
http://unofficialsf.com
Other
571 stars 569 forks source link

Quick Lookup - Error with Empty Default Value #960

Open ghost opened 2 years ago

ghost commented 2 years ago

I have a number of Quick Lookups on a page, on these Lookups I hide and show them based on some previous selections. The lookups use the Default Value field e.g. {!varWorkOrder.WorkOrderNumber}

I have found an issue where if I have a flow which loops me back to this page where the Quick Lookups are, I get an error which says

"Error element Detailed_Information (FlowScreen). The flow failed to access the value for varWorkOrder.WorkOrderNumber because it hasn't been set or assigned."

I only get this error when returning back to the screen and not on the initial loading of the page. AKA when the page first loaded varWorkOrder.WorkOrderNumber never had a value and it loaded fine but the second visit to the page I get the error.

ericrsmith35 commented 2 years ago

Have you tried assigning {!varWorkOrder.WorkOrderNumber} to a flow variable and using that instead for your default value?

ghost commented 2 years ago

Have you tried assigning {!varWorkOrder.WorkOrderNumber} to a flow variable and using that instead for your default value?

Thanks for the quick reply.

I'm not 100% sure what you mean. {!varWorkOrder.WorkOrderNumber} is a flow record variable (set to type Work Order) and it is set to the Default Value field. Depending on where the flow got launched from, this variable may or may not be ever populated with a value.

Screen Shot 2021-11-08 at 11 35 36 am
ericrsmith35 commented 2 years ago

Try creating a new Text variable and use an Assignment node to assign {!varWorkOrder.WorkOrderNumber} to it. Then try to use the new variable as the default in the Lookup to see if it makes any difference in how the flow behaves.

On Sun, Nov 7, 2021 at 7:39 PM CultechPtyLtd @.***> wrote:

Have you tried assigning {!varWorkOrder.WorkOrderNumber} to a flow variable and using that instead for your default value?

Thanks for the quick reply.

I'm not 100% sure what you mean. {!varWorkOrder.WorkOrderNumber} is a flow record variable (set to type Work Order) and it is set to the Default Value field. Depending on where the flow got launched from, this variable may or may not be ever populated with a value.

[image: Screen Shot 2021-11-08 at 11 35 36 am] https://user-images.githubusercontent.com/73424220/140668321-1cafa118-2631-439c-8314-91d0087f9fd4.png

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/alexed1/LightningFlowComponents/issues/960#issuecomment-962716522, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF4UHX4BJTUNXDMG6HGUQYLUK4L43ANCNFSM5HQMVGJA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.