Hello all,

Q1) I want to Know what is the diffidence between using attribute and local attribute in Maximo anywhere app.xml files. 
 Q2) when should I use attribute and when should I use local attribute????

------------------------------
[Abdallah] [Adel]
[Technical consultant]
[MegaSoft]
[Cairo] [Egypt]
[+201112334228]
[a_adel@megasoft-arabia.com]
------------------------------



#AssetandFacilitiesManagement
#Maximo
#MaximoAnywhere

A local attribute is able to be used by Anywhere and typically won't come from Maximo (though it can if you provide the remoteName). It is often used for combination values (like assetnum & description) in a single attribute or for tracking the number of records in a dataset (like number of materials). If the data exists in Maximo as an attribute and you want to be able to update it inside of Anywhere, it should be an attribute.

------------------------------
Steven Shull
Director of Development
Projetech Inc
Cincinnati OH
------------------------------

Another way to think of a localAttribute vs. an attribute in Maximo Anywhere is that a localAttribute is a device side only mechanism or "bucket" whose value will never be passed back to Maximo.  You declare it only in the app.xml and it lives nowhere outside of Maximo
Anywhere.  As Steven said it is often used for summary counts of data sets, value combination of multiple attributes (makes it easier to display concatenated values in a limited space with the various layouts,) and local-only data processing.

------------------------------
Bradley K. Downing , MBA
IBM Certified Adv. Deployment Prof. Maximo v7.6.1
IBM
Bakersfield CA
------------------------------