I haven't a scooby doo what this means. How can a configured dimension conflict with itself?
How can a configured dimension conflict with itself?
Hi Rob, I'd say it's the Reptilians fault, but you won't believe me.
And I seriously think it has to do with derived configurations.
How you create this configurations, manually or you used configuration table?
Sometimes in a hurry we forget about the order of creating configurations derived from the table.
I used a DT. I'm at home now so I can't post it, but how does the creation order affect things? The dimension in question is not driven by the parent - it's configured independently in every config. I've always thought it would be useful for configurations to be able to read state of other configs but thought was impossible.
Retrieving data ...