You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have had multiple requests from my customer for the following feature in Invictus Dashboard. Let me context the situation:
In my current setup (mainly integration) I am logging errors to the dashboard using the ‘Event Text’ property baked in on the Invictus Dashboard:
When the customer has 100+ errors (mostly functional errors so beyond my control) they have to open 100+ entries on the dashboard one by one to check what the error message is. Customer is wondering whether an export feature is in the pipeline/can be added to the pipeline that can export either all properties from detailed info on the dashboard or a feature where you can select what fields to add in the export.
Right now, there is an export functionality, but that does only take an export of the main entry (head level on the dashboard). It does not add the sublevel details.
The text was updated successfully, but these errors were encountered:
I have had multiple requests from my customer for the following feature in Invictus Dashboard. Let me context the situation:
In my current setup (mainly integration) I am logging errors to the dashboard using the ‘Event Text’ property baked in on the Invictus Dashboard:
When the customer has 100+ errors (mostly functional errors so beyond my control) they have to open 100+ entries on the dashboard one by one to check what the error message is. Customer is wondering whether an export feature is in the pipeline/can be added to the pipeline that can export either all properties from detailed info on the dashboard or a feature where you can select what fields to add in the export.
Right now, there is an export functionality, but that does only take an export of the main entry (head level on the dashboard). It does not add the sublevel details.
The text was updated successfully, but these errors were encountered: