Options
  • State Suggested Answer
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 12 subscribers
  • Views 150 views
  • Users 0 members are here
Related

Questions About Dynamic Permissions, Numeric Field Formatting, and Filtering Related Objects

idan tubali

Hello,
We have a few issues that we haven't been able to solve:

We work with many workflows, and the "Assigned To" field is editable by all users, not just the person it was assigned to.
We considered setting permissions for the entire object to only the assignee, but we wanted to ask if there's a "simpler" way to dynamically control permissions specifically for the "Assigned To" field, without affecting the whole object.

We have fields that represent percentages. Is it possible to add a percentage sign (%) next to a real number field (not in the field name)?

In real number fields, there is a comma separator every three digits (e.g., 123,132), but in integer fields, there is no comma separator.
Is it possible to apply the same comma separation to integer fields as well?

In every object, there's a triangle icon next to it showing "Related Objects".
Clicking the triangle reveals all related objects.
Is it possible to hide certain related objects?
We have an object with many links, and we want to show only the "significant" ones.

Parents
  • 0

    I'd try this for assigned to problem;

    1. Put "assigned to" in a group for every class
    2. make that group as "read only" as default. So now, noone can change assigned user
    3. add a lookup named "IsAssigned" with "Yes" and "No" values
    4. Default for this is "No"
    5. Make a second rule on Metadata Configuration to disable read only on this group with "IsAssigned" set to "Yes"
    6. add another lookup named "change assignee" with "Yes" and "No" values
    7. Default for this is "No"
    8. Use property calculator to change this lookup to "Yes" when the user is the assigned user
    9. Do the same for if the user is not the assigned user to change it back to "No"
    10. Tell your users to change "change assignee" to "Yes" to trigger the property calculator
    11. Property Calculator will set "IsAssigned" to "Yes" when triggered. Second MDCC will kick in and make the "Assigned To" editable. 
    12. User assigns the object to another person and saves
    13. Second Property Calculator rule kicks in and sets "No" to "IsAssigned" . The "Assigned To" property is read only again.

    Looks long and complicated but it's only 2 MDCC rule and 2 Property Calculator rule Slight smile

Reply
  • 0

    I'd try this for assigned to problem;

    1. Put "assigned to" in a group for every class
    2. make that group as "read only" as default. So now, noone can change assigned user
    3. add a lookup named "IsAssigned" with "Yes" and "No" values
    4. Default for this is "No"
    5. Make a second rule on Metadata Configuration to disable read only on this group with "IsAssigned" set to "Yes"
    6. add another lookup named "change assignee" with "Yes" and "No" values
    7. Default for this is "No"
    8. Use property calculator to change this lookup to "Yes" when the user is the assigned user
    9. Do the same for if the user is not the assigned user to change it back to "No"
    10. Tell your users to change "change assignee" to "Yes" to trigger the property calculator
    11. Property Calculator will set "IsAssigned" to "Yes" when triggered. Second MDCC will kick in and make the "Assigned To" editable. 
    12. User assigns the object to another person and saves
    13. Second Property Calculator rule kicks in and sets "No" to "IsAssigned" . The "Assigned To" property is read only again.

    Looks long and complicated but it's only 2 MDCC rule and 2 Property Calculator rule Slight smile

Children
No Data
M-Files
M-Files Support


© 2025 M-Files, All Rights Reserved.