đź‘‹ Use this site to provide feedback and ideas for all Nintex Products. See our post on Nintex Community "Welcome to Nintex Ideas" for more details on Nintex Ideas, how an idea is handled by our product teams and more!
If you have questions about Nintex Ideas, please contact ideas@nintex.com
If you require support, please visit Nintex Customer Central
If you have a sales inquiry, please contact sales@nintex.com
While the API integration has all the data I require, the layout/format of the information is not user friendly at this stage. For instance, the incidentfield.fieldlabel has most of the relevant column titles I need but in rows. I needed all the data separate by issue title/Reference ID but currently all the data is in 2 columns.
For example, current API integration format:
Incident ID incidentfield.fieldlabel incidentfield.fieldvalue
1 column a data
1 column b data
1 column c data
1 column d data
2 column a data
2 column b data
2 column d data
3 column a data
3 column c data
I would prefer the format to have 1 row of data per incident ID number:
Incident ID column a column b column c column d
1 data data data data
2 data data blank data
3 data blank data blank
Hope this makes sense.
Thanks for submitting the Idea.
We understand that this would be useful from a usability point of view Due to the technical nature of how the incident fields are stored, it is quite challenging to surface the information this way. We reviewed this during the updates of the API's that are coming soon.
We've thus decided not to go into this direction with our API. We believe that you can use pivot tables within excel or powerbi to accomplish this as well.