• State Not Answered
  • Replies 6 replies
  • Subscribers 87 subscribers
  • Views 1216 views
  • Users 0 members are here

OPPID Properties Priority Ordering

Lee Uy
Offline

someone already post this info but in my case, its not working.

Classes > Plant base Object > named Item > Document > P&ID Document > Properties Tab.
For each property, you have to adjust or add a priority value.
The higher the priority value, the further up the list it will be shown.
The lower the priority, the further down the list it will be shown.

Can someone explain how the "Category" supplemental... Priority works?

  • 0 Offline

    Hello Leslie,

    Depending on which version of OpenPlant PID you are running, the Property Priority is set on the Property Name or by adding Property Priority Custom Attribute.

    Assuming you are running a later version of OpenPlant PID, the Property "priority" is set on the property name itself - see below. 

    When no value is entered, the list order is fairly random. If a value exist, the higher the numeric value, the higher in the Category the property will appear. I suggest you start numbering your desired "top of category" properties, at around 500. Then down from there. I also recommend you leave a space between numbers. First property set to 500, next lower property set to 495, etc. This allows you to insert other properties in between if necessary.

    The Category custom also has a Priority, and this is used to set the order of the Categories in the Properties panel. Keep in mind that this can be easily overridden by the user. They can drag the categories as they need and then perform a Save Settings in OpenPlant PID and override that setting.

    Another important characteristic of the Category custom attribute is naming and what is entered in each of its fields. When adding the Category custom attribute manually, make sure you fill in each field with the exact value as already defined in the out of the box Category. One little difference, and it can result in a new category being created.

    I suggest that when reusing an existing category on a new or existing property, copy it from an existing property to the new one. This can be accomplished as follows.

    In the Class Editor:

    1. Browse to an existing property that contains the existing Category custom attribute.
    2. Click on Custom Attribute... button.
    3. Click on Copy... button.
    4. In the Copy Custom Attribute dialog, double click the custom attribute you want to copy. (In the top pane)
    5. Click Copy at the bottom of the dialog.
    6. Browse to the new property.
    7. Click on Custom Attribute... button.
    8. Click on Paste button.

    This will copy the custom attribute to the property and maintain the field values.

    Breaking down the Category custom attribute.

    Standard: Not used. Leave blank or enter 0.

    Name: The name of the Category (Cannot have spaces in the name)

    Display Label: The name as it is displayed in OpenPlant PID (This CAN contain spaces in the name.)

    Description: Optional. A description of the Category.

    Priority: Defines the position and order of the Category in the property pane.

    Expand: Display the Category expanded or collapsed on startup.

    I hope this helps,

     

    Tony DeRosa

    Senior Application Engineer

    Bentley Plant



  • 0 Offline
    Hi Tony,
     
    First, thanks for your prompt reply to my question.
    I follow all the steps you recommended and stated between 2 places (Property Priority & Category Priority), still not doing the ordering even I specified from 500 with the gap till 100.
     
    My goal to accomplished are the following (OPPID – Equipment): OpenPlant PID with Supplemented (Imperial)
     
    1. Name à Property Priority = 100, à Category Priority = 500
    2. Area à Property Priority = 98, à Category Priority = 495
    3. Device Type Code à Property Priority = 97, à Category Priority = 400
    4. Train à Property Priority = 95, à Category Priority = 350
    5. Number à Property Priority = 90, à Category Priority = 300
    6. Suffix à Property Priority = 81, à Category Priority = 250
    7. Desc 1 à Property Priority = 50, à Category Priority = 200
    8. Desc 2 à Property Priority = 49, à Category Priority = 150
    9. Alternative Name à Property Priority = 1, à Category Priority = 100
     
    Note:
    Red part: is define in other schema (OpenPlant schema)
     
    Steps are:
    1. Name à Property Priority = 100, à Category Priority = 500

     

     

     

    1. Area à Property Priority = 98, à Category Priority = 495

     

     

    1. Device Type Code à Property Priority = 97, à Category Priority = 400

     
    1. Train à Property Priority = 95, à Category Priority = 350

     

    So on….

     
     
    Here’s what the results look like. “Still NOT IN ORDER”.
     
     
    If you have any other solutions or key points, please do not hesitate to contact me at anytime.
     
    Thanks again in advance.
     
    Regards
    Lee
     
  • 0 Offline in reply to Lee Uy

    Hello Lee,

    DO NOT change the priority on the CATEGORY. The properties are what you are trying to "order". As you have done, change the PRIORITY on the PROPERTY only.

    If i get a chance today, I will create a video and post it.

    Regards,

     

    Tony DeRosa

    Senior Application Engineer

    Bentley Plant



  • 0 Offline in reply to Tony D

    Thanks again Tony.

    I redo what you just suggested, by removing the Category Priority to 1 since I cannot leave it blank. Is that ok?

    Let me try that now and let you know the outcome.

    Cheers Mate! 

  • 0 Offline in reply to Tony D

    I tried it with 1 as Category Priority. No changes. Can we do skype call perhaps you can see the problem occurs?

Communities
Support and Services
Training and Learning
Social Media