Topic
SQL SmartObjects are throwing this error on execution:
Inconsistent SmartObject: Mapped Service Object property does not exist. SmartObject: [SmartObjectName]. Service: [ServiceInstanceName]. Service Object: [ServiceObjectName]. Version: []. Property: [PropertyName]
Instructions
All SmartObject properties are mapped to Service Object properties. Service Objects are objects generated by K2 when a service instance is created or refreshed. For SQL Server service instance, K2 fetches a list of all the tables, views, and stored procedures from the SQL database referenced in the service instance, and use that list to generate the Service Objects.
If one property from the Service Object has its name changed, or the property has been removed, executing the SmartObject will result in "Inconsistent SmartObject" error. The following can cause Service Object properties to change:
- Altering a table column name
- Altering a stored procedure's parameters
- K2 is unable to retrieve information about a table or stored procedure
The error message will tell you exactly which SmartObject, Service Object, service instance, and property to look out for. When encountering this error, check the following:
- Make sure there is no issue with the connection between K2 server and your SQL database. You can attempt to refresh the SQL Server service instance your SmartObject is referencing, and see if the refresh operation is able to complete successfully without throwing any error.
- Inspect your table or stored procedure, make sure the column name or parameter is correct and match your SmartObject's properties.
- Use SmartObject Service Tester tool located on your K2 server. Located the service instance, expand it and you should be able to find a list of Service Objects generated by K2, along with the Service Object's properties. You can use this to inspect the Service Object and compare the properties with your SmartObject's properties.
If you have made deliberate changes to your table column or stored procedure's parameters. you need to update your existing SmartObject so the SmartObject is mapped to the correct properties.
If you are still unable to fix the error after checking all the above, you are welcomed to log a support case with Nintex Support to seek further assistance.