search

forcedotcom / devops-center-feedback

61 stars 2 forks source link

Metadata gets pulled with an old API version #221

Closed pklosNxs closed 5 months ago

pklosNxs commented 1 year ago

Describe the bug Flows that are pulled via DevOps Center do not have an XML element "regionContainerType". Therefore, they cannot be deployed when pulled through the DevOps Center into a project running on >=API V55. Probably DevOps Center is using Metadata API V54 to pull the changes because that element was introduced in V55.

To Reproduce Steps to reproduce the behavior:

  1. Create a new Screen-Flow
  2. Add a new screen
  3. Add a section to the screen
  4. Save the flow, running API V55 or V56
  5. Commit the flow via DevOps Center into a sfdx project running API V55
  6. Review the metadata or try to deploy the flow -> regionContainerType is missing

Expected behavior It is expected that metadata will be pulled in the api version that is currently running on production and thus can also be used for further deployments against production

Screenshots Line 33 - Line 53 image

kfidelak94 commented 1 year ago

@pklosNxs - yes, this is a bug we're aware of where we were hard-coded to v53 of the API. This has been fixed in our upcoming GA release (Dec). Sorry for the trouble.

pklosNxs commented 1 year ago

@kfidelak94 Great! Thank you for the update. I'm looking forward to the upcoming release

Schuchie commented 1 year ago

@kfidelak94 which API-Version do you use then (in the dec release), the latest or the used one in the sfdx-project.json?

kfidelak94 commented 1 year ago

@Schuchie If a version is specified in the sfdx-project.json, that will take precedence. Otherwise it will use the latest API version.

Schuchie commented 1 year ago

@kfidelak94 perfect!

TelmoKz commented 1 year ago

@kfidelak94 There is any workaround meanwhile?