Refreshing the DAT file

Aside from a TurboActivate API change, under what conditions should the DAT file for a product be re-downloaded and distributed to end users?

We've noticed that the DAT file contents sometimes change after we update product attributes on the server, but it's not clear exactly which changes affect the DAT file and whether the DAT file needs to be redistributed. Are there any server-side changes that break compatibility with DAT files in the field?

Thanks

We continually update TurboActivate and sometimes that requires changes to the *.dat file. If an old version of the TurboActivate.dat file is failing to load in a new version of TurboActivate, then the solution is to just re-download and replace the TurboActivate.dat file.

>> "Are there any server-side changes that break compatibility with DAT files in the field?"

Nope.

Reply
Discard post