Ensure that Normal MBOs Have Primary Keys

Normal MBOs that have no primary key defined generate a warning message when migrating earlier versions of mobile application projects to Unwired Platform version 2.1 ESD #3. To ensure optimum performance, make sure that normal MBOs have a primary key.

When you migrate a project from an earlier version of Unwired Platform to version 2.1 ESD #3:

• Any normal MBO in the project that does not have a primary key generates a warning message.
• Local business objects without a primary key do not trigger this warning.
• You may ignore the warning on normal MBOs and proceed with the migration. The MBO continues to function as in the earlier version of Unwired Platform, but with performance that is not optimal.
• To ensure optimal performance with migrated MBOs, make sure that all your normal MBOs have a primary key. After adding a primary key, regenerate and redeploy the MBO.

SeeDeveloping a Mobile Business Object in Sybase Unwired WorkSpace - Mobile Business Object Development.