DSO bypassing mapping

[Jim Thwaite]

** Hopefully someone out there has seen this before and has some insight.   We have DSO running between our production system (5.1.2) and a reporting server (6.3)  Overall it works correctly.  The requirement is to transfer EVERYTHING.  So all configuration data and yes even User form data gets DSO'd to the reporting server.   Therein lies the problem.  There are not as many fixed licenses on the reporting server as the production, nor do we want to issue fixed licenses as it is a read only environment.  Obviously a direct field mapping would try to copy the Fixed license and error out the transfer as the license is not available.   We had set up a custom mapping which mapped all the fields straight across except the License Type field.  This is mapped to a static value of Read.  I had this working briefly (Im pretty sure, it was a quick test a while ago, then the project got stalled)  Now when I am testing it to prepare for a rollout it is taking the user data across but it seems to bypass the custom map.   If I filter log it I can see where it performs the DSO process and the mapping is specified in the command line, but the license field is still being carried across with its production system value, not Read.   Any ideas, suggestions, etc are greatly appreciated.   Jim __20060125_______________________This posting was submitted with HTML in it___