RELATED IDEAS
Table View: exporting with FieldTypeId as header
Please, fill in the below fields to enable the processing of your idea.
Who would benefit? |
all users iPMC exporting data |
What impact would it make? |
consistency and compatability with current processes |
How should it work? |
When using Table View, user should be able (to select) exporting data using the FieldTypeId as header (instead of the friendly name + entity) |
Why is it needed? |
consistent with convential way of exporting in iPMC |
The new Table View is a very welcome addition to iPMC.
I foresee that many users will prefer the Table View to make selections and sort these selection of data, to export it and use for further processing outside iPMC, over the conventional way of exporting. Mianly because the Table View UI is visual and user can see immediatly what data is selected and how it would look if exported.
However to be consistent and compatible with current working processes, using the Field Type Id as column header should be allowed.
The user should have the possibility (to select) exporting data using the FieldTypeId instead or the default (friendly) Name.
I Agree with Casper, it will help to import the data again. So the option to have both FieldTypeID + friendly name should be also possible. Now only the name is possible. In the other Export feature you cannot get the friendly field names but only the FieldTypeID, also here you should have both options. Furthermore the Category should also be included so you have the complete structure in Excel to filter your specifciations and after adjusting the data you can easily import the data again.
This would help us as well to easily import the data back when you use the table view exports. Now when you export data using the table view and you want to import it back the system does not recognizes the columns and you need to manual link them.