Why are there duplicate attributes for a local option set in our model environment?

(0) Share

Report

Posted on by Community Member

In our Development environment, we recently changed the values of a local option set. The labels stayed the same. Instead of updating the values of the existing option set in our Model environment, there are now duplicate attributes. One set of attributes maintained the original values and the new set has the new values. This did not happen when we promoted the same unmanaged solution from our Development environment to our Test environment. Does anyone know why this might have happened? Should the guids of these string map values change from one environment to the next?

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (0)

Martin Donnelly 1,030 on at

Like (0)

Report

Never looked at guids of string map; the views and filtered views only join on index and field name IIRC.

Any chance one set was global option set and the other not? Otherwise, I'm predicting someone entered them in Model manually before the update and that your "root" option set value is different between Model and the others.

BTW the "values" of an option set are integers. Certainly you are not referring to the labels as values?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Our model environment is locked down so those of us who would know how to make changes to the option set manually cannot.

When I refer to "Value" I'm referring to the integer. We changed the Value from one integer to another integer.

Was this reply helpful? Yes No
Martin Donnelly 1,030 on at

Like (0)

Report

To me it seems that you've created a new record. As the index value is the key field, changing it seems like a new record with the same label. Again, having never considered the guids in the string table, I can't say that your action traces back to that record. Except that it "worked" for dev-to-test and that I've always deleted the existing option before putting the label on a new index (to synchronize two sets when someone went outside of required procedure), I am not surprised with model; I'm surprised by Test.

Have you checked Model vs Test to see if the differences existed between the targets rather than the action of the solution?

Again, my theory is the there was a divergence between dev and Model that never happened between dev and test.

Was this reply helpful? Yes No
Martin Donnelly 1,030 on at

Like (0)

Report

...or a synchronization between dev and test that never took place for Model.

ps- only platform I have available to me is Online and I'm not up on how to pull string table guids without having the database on premise. I have to leave that sort of experimentation up to you.

Was this reply helpful? Yes No
Kokulan 18,054 on at

Like (0)

Report

If you would like to query and get the values from stringmap you can use XrmToolBox Fetch Builder with the following query or you can modify the query to filter

<fetch version="1.0" output-format="xml-platform" mapping="logical" distinct="true" >

<entity name="stringmap" />

</fetch>

Was this reply helpful? Yes No