Skip to main content
RobertBlakeley
Community Advisor
Community Advisor
May 29, 2026
Question

Issue with custom text values in Classification Set migrations

  • May 29, 2026
  • 3 replies
  • 15 views

I'm sharing in case you run across this issue or have a solution.

 

I've run across an issue with migrating classification rules containing custom text values. If the old rule contains a rule type of Regular Expression and a custom text value in the "To" field, the regex does not migrate.

 

I open the rule in the new Classification Sets interface, go to Rules, then click Migrate. The migration completes but the rule screen is blank with the message “Drag and drop a function to get started”. The original rules are missing. (There is no "try and migrate again" option.)

 

Ok. So, I needed to manually rebuild the rules. (If there had been a lot of rules, that would have been a burden.) I rebuilt the rule, saved the rule, and activated it. Some days later, I checked the report and the report did not show the expected custom value but showed "Unknown" instead. After a week, it still showed "Unknown".

 

I then changed the new rule to use $1 instead of the custom value. I checked the report and that worked. I then changed the rule back to using a custom value, and the rule stopped working, showing “Unknown”.

 

This happened with every classification I tried that had a custom value set in the rule (4 separate classifications). I have submitted a ticket to Adobe.

 

I tried creating a brand-new rule in Classification Sets that used some custom text. That worked.

3 replies

Jennifer_Dungan
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
May 29, 2026

Wow! You should definitely log a bug with client care ​@RobertBlakeley!

 

I haven’t actually attempt any “migration”… I have only created new, and since the “auto” creation of my rules created a dog’s breakfast of a mess, I was planning on re-creating everything from scratch (delete, and recreate)…. I tried once to consolidate the rules it split into three… with no success (and besides, I believe that consolidation needs to leave the original there? Not sure..)

 

Whatever the case, I just planned to do a full review and cleanup of all my rules so that I know they are all correct and still doing what they need to be.

SumitK4
Adobe Champion
Adobe Champion
May 29, 2026

That makes sense to raise with customer care because I noticed something similar as well.

Rebuilding from scratch does seem like the better approach, specially to clean things up and ensure everything is working as expected.

as you mentioned ​@RobertBlakeley  I also did earlier the same instead of trying to migrate the rules, I created a fresh Classification Rule Set and uploaded the old classified file along with some added rules. It worked like a charm.

Honestly, the new setup feels much simpler. No more complex headers like we had in SAINT classifications days and it removes a lot of the automation headache. If you rebuild everything from scratch covering all scenarios, it is much easier to manage and automate going forward.

MandyGeorge
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
May 29, 2026

I’ve heard of a few people having issues with migrating classifications, I’m not looking forward to doing it for my report suites. We don’t have a lot, so I’m considering just documenting them and then creating them all from scratch instead of trying to migrate.

This definitely sounds like a bug, hope they get it fixed!