2 Different View with 1 Same table but need to deny creation on the other view

[win b]

Hi, Can you help me on this scenario? Since im currently working on the Demand Management where in im making a customize Module from the table Demand (dmn_demand). In which i stay all the OOB configurations out of touch from ACL, Table Fields, and Views.

Now here is the challenging part that i encountered so far. Since im on the Demand(dmn_demand) table only difference is the View part which the view i created the Opportunity View in which all my customizations are all there also the modules, and on the OOB View im currently using is the Self-Service(ess) View. Now i already created a UI View for users who have specific role to see the module for Opportunity View and Self-Service View, but some other custom role users only have Self-Service View, and Opportunity View is restricted, and vice versa on this.

Now on the Creation part this is the one im stuck that im still figuring out how can i determine whos who to create since users have one same role on each which is the snc_internal role. 

So to summarize the role here are the ff:
- snc_internal (internal users)
- u_demand_app_manager (custom demand manager)

- u_opportunity_demand_user (custom opportunity normal demand user)

The following scene should be

if the user has role u_demand_app_manager, the user can create both on the table list view on Demand Self-Service and Opportunity View, but if the user has role u_opportunity_demand_user, the user can only create on the Demand Self-Service View and being restricted to create on the Opportunity View. Same goes with the snc_internal user.

What is happening right now is Yes, i applied it on the u_demand_app_manager but on the u_opportunity_demand_user and snc_internal  user i cannot and i dont know where to fix in the first place since im currently lost on what should i call ot need to fix on this scenario.


here are the following screenshots i have to share so you can imagine what im saying

in the Application Nav i already completed this you can see there is No Create New module showing since i applied role on it to be available only on u_demand_app_manager . (thats very easy)

On the Demand view of course this is untouch all users can create on this one.

Now this is the fun part goes in. Inside the Demand table if im viewing as the manager (u_demand_app_manager) this will be what im seeing i can create a New request on the table by clicking the New Button on the upper right of the table of Demand with the View (Default, Self-Service)

same goes when i go with the view for opportunity (but if the user is snc_internal, and u_opportunity_demand_user ) this view or the New Button on the upper right should be disabled.

Since upon checking on the UI Action the New Button on the demand is an OOB field which i dont know how to disable it or make a solution since OOB must not be touched or configured.

And also i created an ACL (Create) and applied role base on the following. So you will expect that there is 3 Create ACL now (1 for snc_internal, 1 for OOB Create ACL, 1 for Demand Manager), then the issue came up the view on the normal demand user seems i get it the New Button is now disabled but creating a normal demand seems restricting me out.

here is the sample acl i created for the demand manager

[Mark Manders]

How do you expect to change OOB functionality if you aren't allowed to change OOB functionality? It's one or the other.

[win b]

@Mark Manders , Like what i said above which i created a new View named it as "Opportunity View" so that i know if im using the OOB Demand vs on my Custom Demand. But only problem is im encountering is limiting on Creating a request upon using the Custom Demand without affecting the OOB Demand.

Its like if you have fields Name as "Address" you can determine it by right clicking and configure dictionary and you will see if the field is OOB or Custom. If the field is OOB it doesnt have u_ in the first name right and only custom fields have u_ on it?

Same goes within the Script, ACL, UI Actions, and Views. if they have an OOB what you need to do is make yourself a customize Script, ACL, UI Actions, and Views pertaining to the original and add validations on it in order to make it more valuable but on my end im currently stuck from which should i need to configure

[win b]

I just found out the solution to this problem. It was on the very own UI Action itself below were you need to include or exclude the views you want to, at first i thought it was very more complicated to do.

[Mark Manders]

You mentioned in your question that OOB was not to be touched and your solution is to update OOB objects?