Dynamic Rename with Change of Data Type - Bug?

[maxksoll]

Hi all,

I just stumpled over an issue where the Dynamic Rename tool destroys my data and increases the required data size by a lot.

The production workflow looks like this:

The incoming data is about 100MB, after the Dynamic Input it is 163TB and after one Select tool (no configuration is applied) back at 100MB.

There are data points missing after the conversion and while debugging there were crazy characters coming out of the tool, but I have no screenshot unfortunately.

What my workflow does in simple words, I am mapping a data file with a mapping file into a pre defined data model, with given types.

Doing so, the typing with the above Dynamic Rename tool and the configuration "Change field type and size" is only working, when I use the mapping from a Text Input tool and not my calculations.

I have no idea what is happening here and I suppose this is some kind of bug unfortunately.

In the attached workflow there are two examples where one is causing the issue and the size is drastically increased from 22b to 5.3MB:

Did someone experienced something similar or can spot the issue here? Would love to use this method for my production workload ...

I am using version 2022.1.1.42590, also tested with 2023.1, if another version works it would also be fine for me.

Thanks a lot in advance!

Max

[apathetichell]

Use a field info to see what's in the description field.

[QuanVuong]

Hi @maxksoll, it seems to me as if the display after the Rename Tool is defect. I don't believe that the data is, in fact, that large (it would probably not fit on your machine, would it?).

Please try to adjust your data types. For me, it resolves both issues in your example file (wrong file size shown, and missing data). Find my little adjustment attached.

[maxksoll]

The field info states that there is no description:

[maxksoll]

Thanks for the response and maybe the example is a little misleading with the conversion between Double and String.

Within the workflow I am performing auto typing based on a automatically read model, which should then enforce the data types to the data.

The number conversion should leave this field empty, but (with newly the attached workflow in this comment) the date field should be populated correctly.

Also what is my main concern here is, why do the results differ at all. It is the same input for the tools, but the results are different...

I hope the new example explains it a little better

[maxksoll]

Just had a chat with @QuanVuong  about the issue and we narrowed it done to receive a message that it states, that it is indeed a bug:

Will raise a support ticket now and post the solution here when it got resolved.

(Attached the final version for the support)

Thanks all