4

A Flow metadata deployment to a Summer 22 (v55.0) org causes an error:

{!FlowScreenFieldName} (Screen Component) - Because the "{!FlowScreenFieldName}" screen field 
on the "{!FlowScreen}" screen is a section, the regionContainerType is required.

What is wrong with Flow metadata if it is fully deployable to previous versions orgs and how to fix that?

1
  • The easiest fix to this issue would be to re-download the flow metadata using 55.0 API version and then it will be downloaded with all tags and structures as per that API version and you can deploy it further to other org again without getting error.
    – VarunC
    Jun 21 at 18:16

1 Answer 1

5

The regionContainerType field of the FlowScreenField metadata component was introduced in API version 55.0. Although it is not documented, when the component type is a Section this field is required.

To fix that simply manually add regionContainerType element with SectionWithoutHeader value to a Flow metadata file:

<?xml version="1.0" encoding="UTF-8"?>
<Flow xmlns="http://soap.sforce.com/2006/04/metadata" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  ...
  <screens>
    <name>FlowScreenName</name>
    <label>FlowScreen Label</label>
    <fields>
      <name>FlowScreenName_SectionN</name>
      <regionContainerType>SectionWithoutHeader</regionContainerType>
      ...
    <fields>
  </screens> 
</Flow>

The easier way would be retrieving Flow instances from updated to Summer 22 sandbox instances if the metadata in the project repository matches the last deployed metadata. After that, all the flow screen sections will be automatically updated with <regionContainerType>SectionWithoutHeader</regionContainerType> element.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.