I am using VB6 to import data into SalesLogix 7.5.1  The problem I am currently having is that none of the 'new' data is syncing out to the remotes, but does show up in the production database. Does anyone know how to get Saleslogix to sync the 'new' data? Is there a flag that can be changed in a table? PLEASE HELP!!!!

Paul:

  How are you connecting to SalesLogix?

  If you are using an SQL Client data won't sync out to remotes. You need to make sure that you connect via the SalesLogix OLEDB Provider, and further more that it is set to Log changes (this would be a default setting).

  Now, once you have Inserted/Updated data into SalesLogix, there are very few options to send it back out to Remotes.

  There is a Way to Resend Accounts to the Remote users (and that will package along all related data) but: It is done per User Per Account (so that could be hundreds or thousands of clicks) and it would take quite a bit to resend over Synchronization.

At this point, your best option might be to Cut New Remote Databases.

I am connecting via a network client not a remote user.

i have cut several net remote databases and tried syncing and the new data still doesn't sync.

What is the way to Resend Accounts? The data that is not syncing is opportunities and there are custom tables.

Hold on.

  If you have cut remote Databases and the Data hasn't been included on their DBs, then the problem could be related to Ownership and/or Subscription Rules.

  Go into the Administrator tool, and then Open up a Remote User's profile. Select the Sync TAb.

  Depending on the Rules applied, the "Accounts" button will be enabled. If it is, you could open it up and then Search for one of the Accounts that you are having issues with (again, assuming this is Account related). You will then see if the User has access to it, if he is subscribed to it, and if you could Resend it (by using the Resend button).

  If the account shows as not being Subscribed, then you should be able to modfiy your subscription rules as needed.

  Now, if these is related to non-Account tables, check the properties of those tables (make sure that they were created with the "Sync" options turned on, etc) - assuming that the tables were created within SalesLogix as well....

VB6 does not synch as far as I know....you need to use a synch aware application that writes data through the SLX OLE DB Provider...... are you accessing the SLX OLE DB Provider....or specifically how are you writing to the SQL Server database???

If your writes are not synch aware you are SOL as far as synching imports.

But you can use VB6, NET, PHP, whatever programming language to upload/edit data to SalesLogix DB and it will sync to remotes, as soon as you connect to SalesLogix OLE DB Provider and not directly to database.

If you are preety sure you are connectin to SLX OLE DB Provider, and data still does not sync, and you have not modified the "Sync" option on tables, then you must check what Raul is pointing about ownership and suscription.

Hi Paul

You could consider importing the data using a sync aware application such as Inaport for SalesLogix (from us). Using such a product generally offers substantial benefits over developing code in VB6, with management, logging, error handlign, and speed of development.

Any questions, please do not hesitate to contact me.

Regards

David Evans

BTW, you can NOT Modify the synch options on a table (OK I haven't tried this in awhile, but in the OLD days this did NOT work, period.....)

......at least it won't affect how the table synchs down the road.....backup the data into a temp table, drop the table.....recreate the table with the correct synch check boxes......bring back the data. And if you want to reshynch the entire contents of the table you can bring in the data from another SLX database via a bundle, install the bundle and it will all synch out (albeit slowly).

And I see my friend David Evans has posted.....Inaport, Scribe, Starfish ETL, Knowledge Sync, Task Centre,  all do a great job of importing data in an SLX Synch aware mode....

Quote: Originally posted by RJ Samp BTW, you can NOT Modify the synch options on a table

Well, i was talking about custom tables.  There are two checkboxes that name "Sync this table out to remotes" and "Sync this table from remotes into main database".

All said, here is the bottom line:

  If you wrote the Data via the SLX OLEDB Provider, it should've sync out to remotes (as long as it met Security and Subscription rules).

  Regardless of how you Imported the data, if you Cut new Remote Databases and it did not make it, then there are 2 potential reasons for it:

  a) The Table that you are working with was not created within SalesLogix so SalesLogix won't include it on new Remotes

  Or

  b) The data does not meet Security and/or Subscription rules, thus is not being included on the Remotes

  The Synch Aware tools are typically a good way to avoid most common problems with the Imports. It is ussually quite obvious how Data Ownership is being assigned (typically defaulting security to Everyone), and some won't allow to work with Tables that were not created (or enabled) within SalesLogix by checking the SecTableDefs and ResyncTableDefs tables to verify the Schema.

Understand, and in the OLD days modifying these check boxes didn't do the trick, you have to modify ReSyncTableDefs directly

....see my previous post.

Writing dates incorrectly formatted as a string  in a  SQL inserted is the number one reason outside code does not synch.....

Quote: Originally posted by Jose Urena Well, i was talking about custom tables.  There are two checkboxes that name "Sync this table out to remotes" and "Sync this table from remotes into main database".

And you cannot modify those once the Table is created. You could only modify them during Table creation.

Now you can!  Good to know that Sage is improving their interface!

I personally don't know that modifying the checkboxes through the interfaces changes the OMNIDIRECTIONAL flag in ReSyncTableDefs and starts\stops synch.

If if does, great!

If you are writing to the SLX OLE DB PROVIDER through VB6 and it still isn't synching....then you will need to look at any DateTime strings being updated\inserted through direct SQL.....

Your update\insert SQL statement will store to the local\main database.....but will NOT synch to the SLX remotes....

The Quasi ISO Date string format for a direct SQL statement INSERT\UPDATE MUST BE (that means NOTHING ELSE will work, no exceptions, full stop, no sync):

"YYYYMMDD hh:mm:ss"

Today's date would look like:

'20120119 09:20:00'

So if the OMNIDIRECTIONAL is correctly set.....and synched out to user's databases......and you are correctly connecting to the SLX OLE DB PROVIDER and issuing Insert's and Updates with correctly formatted datetime strings.....then MAYBE it will sync.

Quote: Originally posted by Raul A. Chavez   If you wrote the Data via the SLX OLEDB Provider, it should've sync out to remotes (as long as it met Security and Subscription rules).   Regardless of how you Imported the data, if you Cut new Remote Databases and it did not make it, then there are 2 potential reasons for it:   a) The Table that you are working with was not created within SalesLogix so SalesLogix won't include it on new Remotes   Or   b) The data does not meet Security and/or Subscription rules, thus is not being included on the Remotes

Actually the third reason (and the one that I see as being most prevalent in the SLX community) is incorrectly formatted Date Time strings in a direct SQL statement.

Probably best to use ADO or a Command Line to Insert \ Update tables through the SLX OLE DB Provider.