Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dictionary item udas keeps getting generated when TransferDictionaryAsContent is true #184

Closed
skttl opened this issue Oct 13, 2023 · 1 comment
Labels
release/10.2.6 release/11.1.6 release/12.0.4 state/sprint-candidate We're trying to get this in a sprint at HQ in the next few weeks type/bug

Comments

@skttl
Copy link

skttl commented Oct 13, 2023

When setting TransferDictionaryAsContent to true, I would expect deploy to stop generating uda files for dictionary items and commiting them to git. But it doesn't.

It doesn't create uda files when creating or saving them, but when I click "Export schema" on the deploy dashboard, they get created/updated for every dictionary item.

Is this expected?

Reproduction

Set TransferDictionaryAsContent to true

Do some changes in the dictionary, create a new item or update another.

Notice no changes to uda files.

Click Export schema on the dashboard.

Notice unexpected changes to uda files containing dictionary items.

Specifics

Deploy 12.0.3

Expected result

I would expect no dictionary-item__[guid].uda files to be created/updated when TransferDictionaryAsContent is set to true

Actual result

It creates/updates dictionary-item__[guid].uda files when clicking "Export schema"


This item has been added to our backlog AB#33779

@AndyButland AndyButland added type/bug state/sprint-candidate We're trying to get this in a sprint at HQ in the next few weeks release/10.2.6 release/11.1.6 release/12.0.4 labels Oct 13, 2023
@AndyButland
Copy link

AndyButland commented Oct 13, 2023

No, it's not expected - as you suggest these entities should be excluded from being written to .uda files when they are being transferred as content. We'll include a fix for this in the next round of patch releases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release/10.2.6 release/11.1.6 release/12.0.4 state/sprint-candidate We're trying to get this in a sprint at HQ in the next few weeks type/bug
Projects
None yet
Development

No branches or pull requests

2 participants