Hi all, In MP24, we added dataset versioning to our dataset exporting functionality. This means that when you export a dataset which has access level Organization or Client/Organization, the checksum of the dataset will be stored in the AD_Dataset table. This information will be used by the Enterprise Module Management window to avoid prompting the user to update the dataset, in the case that the dataset information didn't change from the last time it was imported.
Therefore, it's advisable that if you are going to release a new version of a module which contains a dataset, that you export the dataset before exporting the module. This will automatically add the checksum information to your module Application Dictionary data, and your dataset will be able to benefit from this cool feature. If a dataset doesn't contain checksum information, the Enterprise Module Management will continue to behave as before (the user will be prompted to update the dataset if the module version has changed from the last time he imported the dataset). One final note: the presence of this checksum column doesn't make your module incompatible with earlier versions of MP24. It will simply not be used until the user updates to MP24, and after that the data for this column will be inserted and used. If you have any questions, don't hesitate to ask me. Regards, Antonio. ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ Openbravo-development mailing list Openbravo-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openbravo-development
