Update Custom Data Type from Cluster Force Exact Match - update items order

[bienieck]

Hi,
I would like to show the following problem with the Update Custom Data Type from Cluster tool when updating TestStand container type definition based on LabVIEW cluster.

TestStand creates new container type definition according to the LabVIEW cluster items order. The problem apears after you create the TestStand type definition and then reaorder LabVIEW cluster. After this change in LabVIEW, TestStand will not properlly reorder items in its definition. So for example:

1. We have LabVIEW cluster { 1My String, 2My Numeric, 3My Boolean },
2. Then we create TestStand type from it and we have { 1My_String, 2My_Numeric, 3My_Boolean},
3. Now, we change order in LabVIEW { 3My Boolean, 1My String, 2My Numeric },
4. TestStand do not see change,
5. Then we add new item in LabVIEW { 3My Boolean, This is new, 1My String, 2My Numeric },
6. Update in TestStand will be { This_is_new, 1My_String, 2My_Numeric, 3My_Boolean}.

So at the end we have:

• in LabVIEW : { 3My Boolean, This is new, 1My String, 2My Numeric },
• in TestStand : { This_is_new, 1My_String, 2My_Numeric, 3My_Boolean}.

IMO items order can be sometimes (if not always) important part of good style. That's why I would like to suggest to update also items order if you select Force Exact Match.