ACL Controlled by reference option not working in Yokohama but working in Zurich

[JiotodeM]

We have to differentiate the portfolio data for two groups , sp we created security data filters for that and then we also wanted to separate for Projects/Demands so we tried by controlled by reference option giving pm_portfolio table for two different acls for project/demand but it was working fine in Zurich version but not in Yokohama.

Is there a limitation for this option in yokohama?

FYI - I have used my PDI and it was working in zurich but not in yokohama.

[RaghavSh]

@JiotodeM Can you check if this property helps:

https://www.servicenow.com/docs/bundle/yokohama-platform-security/page/administer/contextual-securit... 

[RaghavSh]

@JiotodeM Please mark the answer correct/helpful to close the thread if your query is answered.

[Ravi Gaurav]

Hi @JiotodeM 

Yes, that’s correct. The “Controlled by Reference” option for ACLs has a known limitation in Yokohama.

In the Zurich release, ServiceNow fixed and enhanced how ACL inheritance works through reference fields, so ACLs set as “Controlled by reference” correctly evaluate the parent record’s permissions (for example, using pm_portfolio for project or demand).

However, in Yokohama, that improvement isn’t applied yet, and the platform doesn’t consistently propagate access from the referenced record. The ACL engine doesn’t fully evaluate reference-based inheritance during record evaluation in some tables, which leads to this issue.

Refer this : https://www.servicenow.com/docs/bundle/yokohama-platform-security/page/administer/contextual-securit...