Maximo

Maximo

Come for answers, stay for best practices. All we're missing is you.

 View Only

  • 1.  Optimal field population - persistent vs non persistent

    Posted Fri March 27, 2026 12:31 PM
    Edited by Saulius S Thu April 02, 2026 01:08 AM

    Hi to the group.

    Would you give me idea which approach would you vote for when designing solution and data presentation in UI:

    a) DBO has two extra fields with persistent storage which are updated by cron jobs from table B based on key; in UI fields are loaded from MBO

    b) DBO has two extra fields which are non persistent and their information is loaded in UI when it is presented

    While approach A adds complexity, data duplication, brings other problems - approach B relies on longer load time.

    What are your criteria, when designing such solutions and making decisions?


    update 2026-04-02 : these fields are purely for "display", no modifications or search option is applicable on them
    ------------------------------
    Saulius S
    ------------------------------



  • 2.  RE: Optimal field population - persistent vs non persistent

    Posted Mon March 30, 2026 06:30 AM

    Hi @Saulius S,

    One important thing to take into account is if this field is a field in a list view (List View in Assets application, etc), so if it is a searchable field. A non-persistent field cannot be searched after by default, extra logic needs to be implemented for it. Also a non-persistent field added in a List View in an application is not performant. So, in this particular case, a persistent field is better, in my opinion.

    Hope this helps.



    ------------------------------
    Liliana Malaescu
    Naviam (formerly known as ZNAPZ)
    Senior Maximo Technical Consultant
    Romania
    ------------------------------



  • 3.  RE: Optimal field population - persistent vs non persistent

    Posted Thu April 02, 2026 01:18 AM

    Hi Liliana, 

    updated question with details: these fields are only for information purpose, no search or "field" property modification is allowed for user.
    In case search was present on data- yes, to some degree I agree with You, however in such case probably logic should be different - adding "search in target table" and link to asset. 
    In case these fields were modifiable - would still question, since partial data copy form source to target table would result that modifications with data could happen in both source/target tables -> as a result this would raise even more questions of data sync.

    However my case is extend data with only extra fields from other mbo's which are ONLY display fields.



    ------------------------------
    Saulius S
    ------------------------------

    Original Message


  • 4.  RE: Optimal field population - persistent vs non persistent

    Posted Thu April 02, 2026 02:47 AM
    Edited by Liliana Malaescu Thu April 02, 2026 02:48 AM

    Hi @Saulius S,

    In that case, i agree with @JULIO HERNANDEZ, that you could only expose those columns using relationships from Object A to Object B.

    Kind regards,

    ------------------------------
    Liliana Malaescu
    Naviam (formerly known as ZNAPZ)
    Senior Maximo Technical Consultant
    Romania
    ------------------------------

    Original Message


  • 5.  RE: Optimal field population - persistent vs non persistent

    Posted Mon March 30, 2026 02:16 PM

    Based on the information provided, it seems like the best approach would be to simply expose the 2 columns from Object B in the UI as "linked" fields using a relationship from Object A to Object B.



    ------------------------------
    Julio Hernandez
    Ergonare, Inc.
    Phoenix AZ
    480-759-9870
    ------------------------------



Related Content