Element Name is the same as another elements description

[PlanningDev]

I have a rule where I am referencing an element but that element's name is the same as another elements description.

Is there a way to force the calc to not work for the other element?

Test
01 - Test (Description is Test)

Rule is applying to both items.

[Michel Zijlema]

I assume that both elements are in different dimensions (as I can't see how you can have two elements with exactly the same name - either as principal element or as alias - in one dimension). In this case making the element unique can be done by prefixing the element with the dimname: [dimname:'element'].

Michel

[PlanningDev]

Both Items are in the same dimension.

The items were added through an .xdi file.

When editing the attributes it adds a numeric key to the end of the duplicate aliases and lets me know it has marked them.

Possibly the ability to add elements through an .xdi doesn't check for duplicate aliases?

[Michel Zijlema]

In your first post you mention you have the elements 'test' and '01 - test' in your dimension, where the description of '01 - test' is 'test'. This should only be possible if the attribute type of description is 'text' instead of 'alias'. In this case a reference to 'test' in a rule would always refer to the principal element 'test' and not to '01 - test'.

Michel

[PlanningDev]

It appears that when creating a dimension from an .XDI I was able to save the dimension even though the name of an element I added was already an alias of another existing element.

Then when going in through architect and editing attributes a window pops up saying duplicate aliases detected and it appends a numeric doe to the aliases that are duplicates and highlights them red. I am allowed to click ok but it doesn't save the numeric code that was appended so when editing the attributes again I am prompted with the window again.

Untill I change the alias duplicate to something else Im guessing it will continue to prompt me.

[lotsaram]

I have noticed this before. I think this loophole/bug/feature exists because XDI sheets pre-date the existence of element attributes or aliases and the Excel 4 macro code has (probably) never been updated.

If yo have created element principal / alias duplicated you do need to fix this, otherwise you will run into other problems on server load and rule compilation and probably more as well.