Hi @Richard Watson, 

Thank you for the post! Can you provide the exact formulas you are using? Do you mind clarifying the issue further? Are you using both formulas?

Hi Kelsey, it may be easier to demonstrate over video if possible?

In my example I have a container (blue rectangle) and inside that, multiple smart containers.  In the smart container selected I have 2 containers (RJ45, SFP28) with 4 items.

If I add a custom property (TEST) to smart container using the formula =CHILDREN.”PORT_NAME” I get an array of the 4 items’ “PORT_NAME” property.

I want to check to see if this array potentially duplicate entries (i.e. someone has accidentally used the same port twice).  To check this I want to use the UNIQUE function to strip any duplicates out.

In this example Gi1/1/1 is repeated.

The COUNT function works correctly to identify there are 4 items in the array.

If I use UNIQUE I’d expect to see any array of 3 items (Te1/2/1, Gi1/1/1, Te3/2/1) - but that is not what happens.  It returns all 4 items including the duplicates.

If I manually recreate the array, the UNIQUE function works fine.

Hope that helps enough to recreate this.  Any suggestions would be most appreciated.
Thank you,

Richard

Hi @Richard Watson,

Thanks for getting back to me with that additional information. I have reported this issue to our development team.

I recognize that this issue may hinder your workflow, and I want to be transparent so that you are able to move forward in the best way possible. Our development team has to rigorously prioritize what to work on based on the extent and criticality of the issue. Because of this, it is not likely that this issue will be resolved quickly. I apologize for any disruption this may cause, and I would like to do all I can to help you continue your work.

As a workaround I would recommend convert the string manually, using =UNIQUE(MAP(CONTAINED.Name, x => ASSTRING(x))) like you did in the last photo.

I will update this thread with any new information about a fix. Please follow along on this thread for updates, and post any additional questions or concerns below.