7/8/2025 5:29:02 PM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss writing script in Architect plugins for SalesLogix & general SalesLogix customization topics (for Windows client only). View the code of conduct for posting guidelines.
|
|
|
|
Problem - TEF files being created in the wrong order on ROS
Posted: 06 Nov 09 6:42 AM
|
Hi all,
Currently I am doing some customizations for a client, while doing so I came across this problem and I hope someone will be able to help out or at least point me in the right direction.
Let me begin from the start and I'll describe the situation.
The customization is similar to the standard Move contact function though supports a few other customizations, hence not using the standard one. Now the problem arised when a workaround was implemented in the customization to resend a contact to a remote database by removing the contact and recreating it with the same data. (if someone knows a better way of resending a contact I'd be happy to hear  )
When testing this all went fine and the contact was properly moved and all data was correctly synced etc.
However a while later one of our data managers in another country(myself and the central servers located in the Netherlands) showed me how the move contact actually didn't properly update the contact field and so the contact contained the old data.
After a lot of investigation the following became clear:
The foreign users use a foreign ROS server (physically located in said country) to make their changes which then syncs this back to our central server. For some reason, this being my problem, the ROS server contains the correctly updated info form the move , however the ROS then proceeds to send the sync files to the central server which are not in the correct order.
For example the wrong order would be:
store old contact data
update contact with new data
remove contact to trigger a resend
re-create contact with the old data
When doing this on the central server the wrong order is similar to the following:
update contact with new data
store contact with the current (updated) data
remove contact to trigger a resend
re-create contact with the current (updated) data
So for some reason our foreign ROS server (and actually there are multiple foreign ROS server showing the same behavior) sends out the TEF files in the wrong order.
If this in any case was already confusing let me make it even more confusing by this example:
When performing the move on the central server with the data manager's login and my own system, all is fine
When performing the move on the foreign ROS server with the data manager's login and my own system, all is fine
When performing the move on the foreign ROS server with the data manager's login and the data manager's system, the problem occurs.
Either way for this I can think of three solutions:
1. Change the customization to resend the contact in a different way, don't know how though.
2. Change the customization to make sure the TEF files are created in the right order on the foreign ROS, don't know how though.
3. Fix the problem in some other setting either on the foreign clients or ROS server.
If anybody could think of anything please let me know, same goes if you would like to know more information, feel free to ask.
Thank you for reading
edit: This is for SLX 6.2.6
|
|
|
|
Re: Problem - TEF files being created in the wrong order on ROS
Posted: 06 Nov 09 6:58 AM
|
I would suggest you use the TranViewer to verify if indeed the TEFF files are generated incorrectly.
There are probably a few other questions regarding how you are doing this.
For instance, on the machine that is "Resending" the contacts, you would want to store the Contact on a Table that does not synchronize (or outside an SLX connection). Then, you would readded via ADODB by creating a recordset and setting each value (INSERT INTO XX SELECT FROM XXBACKUP then you are setting yourself for trouble as you would be synchronizing the statements and each machine would execute with its own data).
Also, is your synchronization setup to sequence files before applying changes? If not, changes may be applied in any order, and if for some reason these group of changes don't go all together in a single file you would then end up with these type of situations as well.
Again, verify your settings, review your code, and check your WGLogs and TEFF files with TranViewer. If that all proves that your code is correct and the TEFFs are wrong, then I would say you need to go to SAGE for this.
|
|
|
|
Re: Problem - TEF files being created in the wrong order on ROS
Posted: 06 Nov 09 7:11 AM
|
Thank you for your reply.
I have checked the TEF files, this is how I concluded the TEF files were generated in the wrong order. The examples I gave is more or less a representation of what is going on.
For your second advice I am not sure what you mean.
In the code I am storing the original contact data in a recordset, deleting the contact and then recreating the contact using the data from the existing recordset.
As for the sequencing, yes this is configured correctly. |
|
|
|
Re: Problem - TEF files being created in the wrong order on ROS
Posted: 06 Nov 09 7:24 AM
|
Question:
Where the WGLog files created properly and the TEFF wrong? Or were both the WGLogs (and consequently TEFFs) wrong?
Then you may have to bring this up to SAGE.
Although I understand that you are storing the Contact's data on a Recordset, are you also storing it on the DB? I am asking because you are referring to the wrong order of steps as "Storing old Contact data".
You have listed the "wrong order" for both server and remote office, but not what the correct sequence should be.
You may have already done this, but seems as if you need someone to review your code and the TEFF files independently (which is something SAGE support may have to do in this case) to determine what is indeed going on. Being on version 6.2.6 i am not quite sure that you may be getting help from them at this point if this is indeed a Logging issue. |
|
|
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|