Learn about known issues and apply workarounds for Unwired WorkSpace and mobile business object (MBO) development.
| CR # | Description |
|---|---|
648243 | SAP data type string (variable length) is detected as STRING(8) The SAP data types STRING and XSTRING (both without length restriction) are discovered in Unwired WorkSpace as STRING(8) and XSTRING(8) respectively. Workaround: Modify the discovered length of the generated parameter or attribute to a length that suits your needs. In the current implementation, any specified length larger than 32767 automatically causes a column of unrestricted length to be generated in the device database. |
621243 |
The deployment and code generation of a mobile business object fails if you name it with one of these words that is a Java datatype or C# value type: binary, boolean, byte, char, date, datetime, time, decimal, double, float, object, int, integer, long, short, string.
Workaround: Do not use these words as part of the MBO name. |
617546 |
An update operation fails if set maxlength for the attribute is less than the length in the enterprise information (EIS) database column.
If rtrim is not used in these cases, the update operation fails with this exception:
com.sybase.vader.da.jdbc.MinCheckAffected RowCountException.null
Workaround: Use the rtrim function in the SQL statement to update operations for char datatype columns, such as:
SELECT dept_id, rtrim(dept_name) as dept_name, dept_head_id FROM sampledb.dba.department |
613403 |
When generating MBO attributes from an Adaptive Server Enterprise table, Visual SQL may display a SQLSTATE=42000 error message.
Because Unwired WorkSpace cannot retrieve the datatype of the parameter in the where clause when you access Visual SQL, the datatype is set to String by default, which can lead to a type conversion error. Workaround: Ignore the warning message. The MBO is created successfully. |
611864 |
When you drag and drop a stored procedure that uses one of several datatypes as a parameter or returns a resultset with a column of one of these types to a new MBO, the resultset contains only the RETURN_VALUE row.
The affected datatypes are: long varbit, varbit, uniqueidentifier, xml, long nvarchar, nchar, and nvarchar. Workaround: None. |
594744 |
The correct Date/Datetime/Time datatype cannot be retrieved when you create an MBO; the datatype is incorrectly set to string.
When you edit an MBO definition you see Data source or definition has changed. Do you want to refresh and remap?. If you select yes, an error message similar to The metadata is not in sync with the backend data source appears. This error is caused by a JDBC driver limitation.
Workaround:
|
584645 |
Use the rtrim function in relationships between two string attributes that map from a char field.
When the enterprise information system (EIS) is a SQL Anywhere database and you create a relationship between two string attributes that map from a char field, and the nullability setting for the char field in the parent table is not null, the char field in child table is nullable. The relationship does not work. Workaround: Manually update the query statement for the parent MBO to apply the rtrim() function to the char field in the column list. For example, if the original query for the parent MBO is:
select region from sampledb.dbo.sales_regionsupdate the SQL statement to: select rtrim(region) as region from sampledb.dbo.sales_regions |
642942 | Cannot generate code with Javadoc option enabled to a folder containing Chinese characters When using the code generation wizard, if you enable the option to generate javadoc, you cannot generate the code to a folder containing Chinese characters without first changing the Language for non-uniode programs to Chinese. Workaround:
|