By default, when device groups at different levels in the Device Group Hierarchy have an object with the same name but different values (because of overrides, as an example), policy rules in a descendant device group use the object values in that descendant instead of using object values inherited from ancestor device groups. Optionally, you can reverse this order of precedence to push values from the highest ancestor containing the object to all descendant device groups. After you enable this option, the next device group commit replaces any overridden objects in the descendant device groups with the inherited objects.
If a firewall has locally defined objects with the same name as shared or device group objects that Panorama pushes, a commit failure occurs. If you want to revert a specific overridden object to its ancestor values instead of pushing ancestor values to all overridden objects, see Revert to Inherited Object Values.
Manage Precedence of Inherited Objects
Select Panorama > Setup > Management and edit the Panorama Settings.
If you want to reverse the default order of precedence, select the Objects defined in ancestors will take higher precedence check box. The dialog then displays the Find Overridden Objects link, which provides the option to see how many overridden (shadowed) objects will have ancestor values after you commit this change. You can hover over the quantity message to display the object names. If you want to revert to the default order of precedence, clear the check box.
Click OK and Commit, for the Commit Type select Panorama, and click Commit again.
( Optional ) If you selected the Objects defined in ancestors will take higher precedence check box, Panorama won’t push the ancestor objects until you perform a device group commit: click Commit, for the Commit Type select Device Group, select the desired device groups, and click Commit again.

Related Documentation