Re: DSO bypassing mapping

[Heider, Stephen]

** *I have not worked with DSO.   What about this: Free up 1 Fixed license on the reporting server.  Create a Trigger on the User table (SQL table) that fires on insert/update that changes the license type to 0 (Read)?  In theory when DSO pushes a new user or updates an existing user in the User form on the reporting server Remedy would assign that user a fixed license, then SQL would immediately remove that license.... so, there would also be 1 available fixed license.   Another option might be to export the Users from the production server and then import into the reporting server.   Stephen       From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Jim Thwaite Sent: Friday, May 12, 2006 9:02 AM To: arslist@ARSLIST.ORG Subject: Re: DSO bypassing mapping ** Unfortunately no, because if the record is passed with a Fixed license and there are none available on the server then the DSO transaction will fail :( ----- Original Message ----- From: Heider, Stephen Newsgroups: public.remedy.arsystem.general To: arslist@ARSLIST.ORG Sent: Friday, May 12, 2006 8:58 AM Subject: Re: DSO bypassing mapping ** Jim,   Could you create a Filter on the reporting server User form that sets the License Type to Read as records are inserted/updated/merged?   Stephen From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Jim Thwaite Sent: Friday, May 12, 2006 8:55 AM To: arslist@ARSLIST.ORG Subject: DSO bypassing mapping ** 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___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___