Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

What is the best way to create or differentiate unique records when creating and loading to a table?

Summary:

There is new development for Humana's EDMCS tool. Up until this point EDMCS has been governing and maintain the Chart of Account structures, with unique and different Core.Names per node. Also, EDMCS has been maintaining simple crosswalk tables, leveraged for mappings in external systems. The current tables also contain records, each with a unique Core.Name per node. In the past, when we found that the Core.Name in the tables could not be used as the "Key" , meaning it would not be unique for each node, we simply concatenated the Core.Name properties with

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!