ALM Transport from Development to Production

John Hughes · 2025-02-25T18:11:02+00:00

There was an error rendering this rich post.

I've used the Data Model and Capsule snapshots and transport packages in the past without any issues. However, I'm having an issue with one where our development environment (14.1.0.0.161052) is now on a different version than our production environment (14.1.0.1.240135). I created the data model package and moved it from dev to prod first and everything looks fine. Then when I create the transport for the capsules it moves everything over, but the objects all say, “Check the layout configuration” and don’t display any data. The data readers have been run, and the cubes have data in them. Does this have something to do with the versioning of the dev site versus production?

When I was doing the capsule comparisons it showed where it was going to create and update screens on the Summary tab, but then at the Info tab it said no changes. But it did create the screens.

Find more posts tagged with

Accepted answers

All comments

Hamza Mesbahi

Hi @John Hughes, from when I've seen this happen (all objects showing "check layout configuration"), it's because the screens were pointing to a different data model than what the initial objects were pointing to. Can you confirm, on any of the screens in the capsule(s) you transported to your target environment (where you're seeing this issue), does the screen properties section show the correct data model that the screen and its objects need to point to?

This process usually happens automatically, i.e., whatever data model the capsule points to in the source environment should remain the same in the target environment. However, since you mentioned a slight misalignment in Board Versions, that could be contributing to the issue.

John Hughes

The model that was created in the dev environment was put in all caps. When I created the model in production, it just capitalized the first letter of the name. I deleted that model and capsule and reloaded it with all caps and it appears to have brought it over. I didn't know that it was case sensitive.

Hamza Mesbahi

That can easily be glanced over. Glad it's resolved!
Best,
Hamza