One other thing I forgot to mention. I have not had to do this yet, but if I do I know I can.
We use one coding method for all surveys. As we add clients, if they have an XIN we modify their alpha codes to match the ones we currently use. At some point, I may need to split codes in our standard so we can collect for the two different clients. If that happens, I could use an exported XML Report to recombine the split codes.
For example, we shot BC and TC for Bottom and Top of Cub and use attributes to identify concrete or asphalt, since the client does not used different symbology by type. If a new client does draw concrete curbs on a different level, we might need to create two alternate codes and for the one client, they both point to one feature but on the other they point to two. However, if the client with one feature requires only one alpha code, after the fact we can export a new RAW file where the alpha codes are combined into a single code.
Or, I can use the attribute values to direct an output report to substitute one of two alternative codes. Then, upon re-import, one code with two attributes becomes two codes.
Next to OpenRoads technology, XML reports are one of the greatest tools of InRoads and need to remain in the product. And as you move forward, should be made part of more of the tools, rather than less.