Hi Everyone, A bit of a hybrid question - I am developing an app where I need an account to have an attribute / property that can be modified as the business needs. The standard account entity does not have this attribute (which would have a 4 selection ENUM). Reading up on this my approach is to extend the Account entity and add the property I need to create a specific account / user type for our business. I have created this entity in one of my custom modules and am intending to apply it to the app level security role(s). Further, some rows of data will need to be visible ONLY if the ENUM selected in the Account entity meets certain criteria - e.g. Salesperson OR Sales Manager. I've been told that a Microflow to feed a list would be a best approach for this. So, my question is twofold. Am I heading in the right direction regarding extending the base account entity / object or is there a better way to approach this? If not, will I need to create custom entities for all my role types? Secondly, are there limits to the number of rows I can comfortably return in my Microflow to support this without creating performance bottlenecks. This is a bit of an odd question, but I need to ensure I get security - particularly data access - right from the get-go for this app. Thanks!
↧