We've noticed something unexpected happening in some of our FTP classification imports.
Our process was to download the browser template to obtain the SAINT header, including these two values:
We then include all the keys and classifications and upload this to adobe. This has been working well for years, but we've recently noticed that the header returns A:0:0 for most report suites now.
we're concerned that this is affecting classification.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Hi @upliftertom ,
Can you share more details on classification discrepancy noticed, it would help narrow down if this is due to some other reason and not file header.
In my prior experience, I have mostly downloaded template once and reused on multiple occasions, It never caused any issues so I assume the discrepancy could be due to some other delimiter / character in values.
Views
Replies
Total Likes
The second example is from downloading the template. It also shows as 0:0 when doing a browser export.
We've noticed some issues with missing classifications. I've asked a question previously about this:
If that id is a reference, I would not expect it to be set to A:0:0
Views
Replies
Total Likes
Had an update from Adobe. They have updated their systems to improve processing time for backend systems and it's no longer necessary anymore to have the report suite numerical identifier anymore. A:0:0 should work (or even whatever it was set to before).
Views
Replies
Total Likes
Views
Like
Replies