You need to sign in to do that
Don't have an account?

flow screen duplicating
I have a flow that seems to run pretty smoothly, but for some reason with a few accounts, I get this error.
Not only that, it meets requirements to go to the next steps through the flow, but instead brings me back to the same screen, but duplicated at the bottoms. This is not how it was built and nor is the screen built like this.
Pictures below. I have highlighted in red what the original screen contains.
Has anyone had this before and how could I fix this?




Not only that, it meets requirements to go to the next steps through the flow, but instead brings me back to the same screen, but duplicated at the bottoms. This is not how it was built and nor is the screen built like this.
Pictures below. I have highlighted in red what the original screen contains.
Has anyone had this before and how could I fix this?
Regards,
Salesforce support
It's: 00D8E000000FSfG
Thank you
S1 UI Platform ClientSidePresentationException Error in serviceComponent://ui.interaction.runtime.components.controllers.FlowRuntimeController/ACTION$executeAction ( DeviceType: LARGE AppName: one:one)
lib.gack.GackContext: java.lang.IllegalArgumentException: unable to find element for complex reference: Get_Opportunity.Occupancy_Status__c
If you find the information helpful mark it as the Best answer.
unfortunately not. That doesn't even relate to the actual section of the flow.
Thanks for the response. It seems like you've already found a workaround, but in case it's helpful for you, I posted about a similar flow error, and someone was able to track the error back to userLocation: https://developer.salesforce.com/forums/ForumsMain?id=9062I000000DHNzQAO.
While I don't reference userLocation in my flow, I had an assignment at the beginning that retrieves {!User.Email} and stores it in a variable to later retrieve all records with that email. I changed this so that the user types their email address in an Email field, and then I use their input to pull records with their email. For now it seems to have solved my problem, and although I'm not quite sure why, referencing User was the issue for me.