Cache Validation Rules and Error Messages

These validation rules apply to cache groups and cache update policies and are enforced during MBO development and, in some cases, when you deploy the MBO to Unwired Server. Messages are generated when validation rules are violated.

Cache group and cache update policy validation rules and error messages
Severity and message	Cause	Action
Error: Invalid interval for cache '<CacheGrp Name>': the value of interval must be between 1 and 2147483647 seconds.	The cache group's cache interval is out of range.	Specify a valid cache interval.
Error: Cache group name cannot be empty.	The cache group name is empty.	Enter a valid name.
Error: Invalid cache name: '<CacheGrp Name>'. A valid identifier name must begin with an alphabetic character or an underscore, followed by alphanumeric characters or underscores.	An invalid cache name is specified.	Enter a valid name.
Error: Invalid cache name: '<CacheGrp Name>', name cannot be a Java or C# language.	The cache group name is a Java or C# keyword, such as binary, boolean, byte, char, date, datetime, time, decimal, double, float, object, int, integer, long, short, string, switch, and so on.	Do not use Java or C# keywords as cache group names.
Error: Invalid cache name: '<CacheGrp Name>', the length must be less than 64.	The length of the cache group name is longer than 64 characters.	Enter a valid name that is shorter than 64 characters.
Error: Duplicate cache group name: '<CacheGrp Name>'.	Another cache group uses the same name.	Enter a unique and valid name.
Warning: Relationship from 'MBO1' to 'MBO2' references to different cache groups. Mobile business objects with relationship should be grouped in the same cache group.	MBOs in a relationship are in different cache groups. This is allowed, but be aware that MBOs in different cache groups may use different cache refresh policies.	Move the MBOs within a relationship to the same cache group if they need to share the same data refresh schedule.
Warning: ‘CREATE’ operation '<Oper Name>' has 'Apply results to the cache' option set without returning primary key fields.	A create operation uses the "Apply results to the cache" cache update policy, but the MBO to which it belongs does not have a primary key.	Set a primary key for the MBO in the Properties view from the Attributes > Attributes Mapping tab.
Warning: The output record of the ‘CREATE’ operation '<Oper Name>' with 'Apply results to the cache' option set does not contain the primary key columns.	The output of the create operation that uses the Apply results to the cache cache update policy does not contain the primary key columns.	Change the definition of the Create operation so the output covers the MBO primary key columns. Note: This rule applies only to non-JDBC data sources. For JDBC data sources, since Unwired WorkSpace cannot identify the output metadata of an operation without executing it, you must verify that you have correctly defined the operation.