Maximo

We are facing an issue in Maximo Mobile where two asset applications, which are configured for different sites, are showing inconsistent data. Specifically, when both applications are published to the mobile platform, only the application published last displays data, while the other remains empty. After investigating the problem, we found that the API call made by the mobile app includes "oslc.select=undefined," which could be the reason for this issue but, we are not sure. What could be the underlying cause of this data issue?

------------------------------
Anbukkarasu M
------------------------------

We ran into the same issue before. Both Apps cannot share the same main object structure. Duplicate the object structure and change one of the Apps to use the newly created OS and then you will see data on both Apps. 

We are facing an issue in Maximo Mobile where two asset applications, which are configured for different sites, are showing inconsistent data. Specifically, when both applications are published to the mobile platform, only the application published last displays data, while the other remains empty. After investigating the problem, we found that the API call made by the mobile app includes "oslc.select=undefined," which could be the reason for this issue but, we are not sure. What could be the underlying cause of this data issue?

------------------------------
Anbukkarasu M
------------------------------

Hi Stephen,

Thanks for your response, we already have two different main object structures for both the application, yet we are facing the same issue.

We ran into the same issue before. Both Apps cannot share the same main object structure. Duplicate the object structure and change one of the Apps to use the newly created OS and then you will see data on both Apps. 

We are facing an issue in Maximo Mobile where two asset applications, which are configured for different sites, are showing inconsistent data. Specifically, when both applications are published to the mobile platform, only the application published last displays data, while the other remains empty. After investigating the problem, we found that the API call made by the mobile app includes "oslc.select=undefined," which could be the reason for this issue but, we are not sure. What could be the underlying cause of this data issue?

------------------------------
Anbukkarasu M
------------------------------

There's a couple of concepts here. The same main object (IE ASSET in this case) cannot use different object structures for transactional data until 9.0. Even then, I wouldn't typically recommend it. 

Transactional data does not merge the oslc.select across applications like we do for lookup data. When you synchronize an application's data (using check for updates or the Data Update screen or one of the other sync processes), we will retrieve it using the schema for that application. If you have the same asset returned by different applications and have different fields defined in those applications, you will get back null values in the fields that were not part of the app that was last synchronized. Each transactional record will exist in the database in 1 row whether it's requested by 1 app or 5 apps. There is a tagging mechanism that occurs that defines which applications and datasources retrieved that record which is how we know when to display the record. We don't store the data multiple times to avoid someone modifying the record in one datasource and not seeing it when they switch to another datasource that also contains that record. 

Hi Stephen,

Thanks for your response, we already have two different main object structures for both the application, yet we are facing the same issue.

We ran into the same issue before. Both Apps cannot share the same main object structure. Duplicate the object structure and change one of the Apps to use the newly created OS and then you will see data on both Apps. 

We are facing an issue in Maximo Mobile where two asset applications, which are configured for different sites, are showing inconsistent data. Specifically, when both applications are published to the mobile platform, only the application published last displays data, while the other remains empty. After investigating the problem, we found that the API call made by the mobile app includes "oslc.select=undefined," which could be the reason for this issue but, we are not sure. What could be the underlying cause of this data issue?

------------------------------
Anbukkarasu M
------------------------------

Hi Steven Shull,

Thanks for your response, in such case we have also duplicated Technician application as well which is showing data in both OOB and custom one.

As per your explanation, verified the schema and found that it is having details related to recent published app, but is there any way we can fix it?

There's a couple of concepts here. The same main object (IE ASSET in this case) cannot use different object structures for transactional data until 9.0. Even then, I wouldn't typically recommend it. 

Transactional data does not merge the oslc.select across applications like we do for lookup data. When you synchronize an application's data (using check for updates or the Data Update screen or one of the other sync processes), we will retrieve it using the schema for that application. If you have the same asset returned by different applications and have different fields defined in those applications, you will get back null values in the fields that were not part of the app that was last synchronized. Each transactional record will exist in the database in 1 row whether it's requested by 1 app or 5 apps. There is a tagging mechanism that occurs that defines which applications and datasources retrieved that record which is how we know when to display the record. We don't store the data multiple times to avoid someone modifying the record in one datasource and not seeing it when they switch to another datasource that also contains that record. 

Hi Stephen,

Thanks for your response, we already have two different main object structures for both the application, yet we are facing the same issue.

We ran into the same issue before. Both Apps cannot share the same main object structure. Duplicate the object structure and change one of the Apps to use the newly created OS and then you will see data on both Apps. 

We are facing an issue in Maximo Mobile where two asset applications, which are configured for different sites, are showing inconsistent data. Specifically, when both applications are published to the mobile platform, only the application published last displays data, while the other remains empty. After investigating the problem, we found that the API call made by the mobile app includes "oslc.select=undefined," which could be the reason for this issue but, we are not sure. What could be the underlying cause of this data issue?

------------------------------
Anbukkarasu M
------------------------------

Hi Stephen,

Thanks for your response, we already have two different main object structures for both the application, yet we are facing the same issue.

We ran into the same issue before. Both Apps cannot share the same main object structure. Duplicate the object structure and change one of the Apps to use the newly created OS and then you will see data on both Apps. 

We are facing an issue in Maximo Mobile where two asset applications, which are configured for different sites, are showing inconsistent data. Specifically, when both applications are published to the mobile platform, only the application published last displays data, while the other remains empty. After investigating the problem, we found that the API call made by the mobile app includes "oslc.select=undefined," which could be the reason for this issue but, we are not sure. What could be the underlying cause of this data issue?

------------------------------
Anbukkarasu M
------------------------------