Deprecated fields breaks Flows in Winter'24
Hi All,
There is a known issue which, in my opinion, is quite serious affecting Winter'24 orgs. https://issues.salesforce.com/issue/a028c00000xFymVAAS/ Essentially, "Get Records" element in Flow fails when trying to access a deprecated field from a managed package. Even if you're not using the field directly in your flow, if you are passing the result of "Get Records" to a subflow, the issue occurs. This is not an uncommon use case, in my opinion, and I am afraid this will affect several customers. The workaround suggested is not feasible to be implemented and tested within this short time span. I am not sure what action can be taken here but wanted to highlight this to increase awareness and start a discussion. Unless I am missing something, this looks to be a major issue.
