Provisioning Omada Identity Suite Data for Development and Test?

• 
  Hi @AndrewC thank you for your post!
  By correlated changes do you mean, for example, having a FirstName column, LastName column and an XML field in which FirstName and LastName both exist and you need to sync the masking internally to the XML as a result of what the FirstName and LastName get masked to in the separate columns? 
  Or do you mean that you just need something that is capable of masking both standard fields and also XML fields?
  Thank you very much.

  PlantBasedSQL November 05, 2018 16:15

  - 0 +
• 
  @dOCTOClone Hi Doc,
  
  I'm only starting to get into the Omada Infrastructure so my understanding might be incomplete but yes, your first scenario is the kind of thing I am told we are looking at. There are further complications but I want to cross each bridge one at a time.

  AndrewC November 05, 2018 22:01

  - 0 +
• 
  Thank you for clarifying @AndrewC
  That makes sense - so in either case we are able to mask the XML, however obviously the second scenario is considerably simpler and involves using an XML masking rule in Data Masker.
  For the first scenario i described and the one you mentioned, the solution would be to use a Synchronisation manager rule, i.e. take a substitution rule that is masking a regular column (one that also appears in the XML) and then convert it into a sync manager, using a Table-To-Text rule to then sync the same value across both the regular column and the XML.
  You can find more information on the Sync Manager rule here: https://documentation.red-gate.com/dms6/data-masker-help/version-6-tech-tips/how-do-i-synchronize-changes-to-an-item-with-no-logical-join
  But if you need further information on this please feel free to let me know!
  Thank you very much.

  PlantBasedSQL November 07, 2018 16:11

  - 0 +
• 
  Thanks Doc, yes, that does look like it should handle the problem, even though it will require a ton of man hours to implement. Might be an interesting job to set it up, for someone of that kind of mind

  AndrewC November 08, 2018 11:00

  - 0 +
• 

  Hi Andrew,

  You're absolutely right — dealing with structured and semi-structured data like XML fields within products such as Omada can make data anonymization a lot more complex than it first appears. I’ve worked with a similar scenario where correlated data needed to remain logically consistent after anonymization, which required building a custom mapping layer to handle both relational tables and nested XML content.

  In our case, we couldn’t rely on out-of-the-box anonymization tools alone. We had to develop tailored scripts that could identify dependencies across fields and maintain referential integrity after the data was masked. If your customer has sensitive identifiers or personal data in XML blobs, I’d suggest starting with a detailed schema audit to locate high-risk fields before deciding on the anonymization strategy. Tools like SQL Clone can still be valuable in this setup, but the anonymization phase definitely needs more careful customization.

  On a side note, while diving into all of this, I found myself asking totally unrelated but equally complicated questions — like lgs sonuçları ne zaman açıklanacak 2025? Just shows how timing and accuracy matter in many areas, whether it’s in handling production data for testing or waiting on nationwide exam results. 

  rjson July 10, 2025 18:35

  - 0 +

Add comment

Please sign in to leave a comment.