To homepage To homepage

For "Add New Table" or the "Add New Table with Field Selection" option, the fields are either randomly arranged or aligned with the source database.

  • 17 October 2023
  • 3 replies
  • 56 views
sierd.zuiderveld
Rank
Userlevel 3
Badge +1

We have observed an inconsistency in the field order when adding a new table from the ODX to the DSA. Depending on whether we use the "Add New Table" or the "Add New Table with Field Selection" option, the fields are either randomly arranged or aligned with the source database.

When we use “Add New Table” we notice that all fields are somewhat randomly arranged. 

When we use “Add New Table with Field Selection” and then check all the boxes the order is exactly as in the source database (as expected). 

 

How come that there is a difference? Is this on purpose? Thanks

 

(TimeXtender 6346.1)

3 replies

kerry_bespoke
Rank
Userlevel 1
Badge

Hi @sierd.zuiderveld 

We are experiencing the same issue in our V21 environment. Did you ever get a response on this?

Seems weird that the default option to copy in a table to TX from the ODX would scramble the field order.

Kerry

Kerry // Bespoke Analytics
rory.smith
Rank
Userlevel 5
Badge +7

Hi all,

 

are you experiencing this for every data source type coming from ODX? I have not actively noticed this with SQL tables, dragging them directly does not seem to change the order with respect to BU for me.

It would not surprise me if the lack of field order in the parquet standard is involved as a field selection needs to explicitly subselect where a whole table extract may just follow parquet order which is probably library dependent.

kerry_bespoke
Rank
Userlevel 1
Badge

HI @rory.smith 

Thank you for your quick response on this…

Our source is actually Excel and is happening with every table from that data source.

Kerry

Kerry // Bespoke Analytics

Reply


Terms and ConditionsCookie settings