RELATED IDEAS
Field Revision Notes so we can know why a value was changed with more specificity
Please, fill in the below fields to enable the processing of your idea.
Who would benefit? |
Developers making automated attribution changes as well as anyone investigating product data issues. |
What impact would it make? |
Increased transparency and communication, and a debugging gamechanger for automation. |
How should it work? |
When updating a field value via UI, import tool, or API, a user should be able to leave a note explaining the revision. |
Why is it needed? |
If a business has multiple automated scripts making attribution changes, it can be challenging to debug issues without this form of logging. |
Along with Value, Modified date, Modified by, and Restore, I would love a new column in the Revisions panel for a note, giving the user a chance to document why that revision was made.
This would be a lifesaver for any InRiver user who has implemented a bunch of automated scripts that ping the REST API with attribution changes. Oftentimes an attribution issue will be noticed from within the InRiver UI, with the only clue being who made the change and when. This is especially hard to debug when the "who" is simply the name given to the API key that was used to make the change. If that same key is used across many automations, it can be really hard to track down the source of the issue.
The revision note could be passed as an additional parameter to the Put:fieldvalues endpoint. Manual revisions in the UI could support these as well. Mass updates, etc.
