I'm using #Copado
to try to move a screen flow up to the next environment. I get no issues when I debug or when I run the flow on the record page. However, when I go to deploy it, I get an error on a table component. The component displays records from a GET & is meant for users to review existing records to make sure they actually need to complete the flow.
It failed when it was on a separate screen. It is failing when added to this screen. It failed as view only, single select, & multi-select. It failed when storing specific fields and all fields. I tried moving it back an API version (as that has resolved other issues with other flows), but it wouldn't let me save.
Turns out my co-worker previously had an issue deploying flows with data tables on API 65. He was able to save as API v64 & deploy. I get errors on all the tables.
When I validate the move directly from one sandbox to another (without going through any kind of source control) via Gearset, it shows no issues. This leads me to believe y'all were right about the root cause being the API version of source control. That said, we're setting up a new repo to use w/ Gearset & we're not supposed to move work until that's all done, so I don't know that it's worth going down the full resolution rabbit hole.
