 Importing Org Structure data
Do you have any kind of "best practices" around importing org structure data (for the RBS and/or general resource attributes) and dealing with changes? What are all the things I need to consider when working with this? This seems like it would be a common concern...
Here's my situation:
I need to import Organization structure data from another data source which will populate the structure into the RBS lookup table, which will be used for RBS and possibly also some other custom fields will reference this as well. However, my current client's org structure changes frequently, so I'm unsure how I'm going to maintain the lookup table automatically (and I assume I'll try and keep the resource's attributes updated automatically, too, if I can). So obviously, I don't want to screw up the RBS and mess up the security there when the info changes, but I need to keep current information. Am I going to be stuck with building the list, then manually maintaining it from then on? Also, would you recommend using two separate lookup tables for RBS and for "Client Office" (we could call it whatever...)
TIA!
~Jimbo
 |