In PSE, you can right click an element reference > Convert > Change Reference Type... and have the option to make your current element reference the Primary Parent via a check box. This functionality is not replicated in PI Builder. Thus, you have to do this in 3 steps:

1) Delete the Element Reference
2) Publish primary parent with the NewParent column set to the path where you would like the primary parent to be
3) Add an Element Reference to the Primary Parent at its new location.

This is a bit cumbersome to accomplish the same thing as a check box in PSE.

I tried to look but didn't see this requested. It would be very useful if the values of the variable(s) created in an Analysis could be accessed from the Manage Formats page of a Notification Rule. I know you can create output attribute and map the output of an Analysis to an attribute, then reference that from the Manage Formats page. However it would be much better if any variable created in the Analysis that is tied to the Notification Rule could be accessed when creating the email format. This would provide an easy way to for example create a variable for 1 hour average of a tag and then be able to include the value of this variable in the email. If for example the Content section of the Manage Format page would have a section called "Referenced Analysis Variables" that once expanded would include the variable names of all variables created in the referenced Analysis. Then could drag and drop the variable value(s) and/or timestamp(s) into the email message the same way you can the other referenced properties of the items.

This request originated from a tech support case where the objective was to remove the delete permission from all users (including admins) at all levels (server and databases) to prevent any objects from being deleted. The desired behavior in this case would be that by default, no one should be able to delete any objects, and if needed the permission would be temporarily added to the Administrators identity and then removed when the necessary deletion was completed.

Any identities with the Admin permission were able to delete objects, even if the delete box was unchecked, due to the Admin permission being present, which allows to change and overrides other permissions.This behavior is intended, since Admin permission allows to change any permission.

This enhancement request consists of adding a visual indicator in PSE to indicate that the Admin permission for an identity will override other permissions, since this is not always intuitively understood that way. Examples of this could be changing color/graying out other permissions for identities with the Admin permission or expanding the descriptor that comes up when the mouse is hovered over the Admin permission to include this information.

Schedule data archive shifts occur and create archive files based upon a Minimum Archive Size calculation. This calculation is based upon the total count of record numbers. When large amounts of tags are deleted, the total number of tags is reduced but the record number count remains the same...thus creating a huge discrepancy between the two counts.

The minimum archive file size is based on total record numbers. Thus, if you delete a large number of tags (e.g. Reduce a 5M tags system down to 1M tags after splitting a collective into multiple collectives)....then the system will artificially create very large archive file sizes which are filled at a low percentage. This calculation result is different from the Archive_AutoArchiveSize calculation which looks at the count of active tags. The deviation between the two leads to confusion and difficulty properly scheduling archive shifts, along with generating incorrect % full results (which look at the total record number count, not the total tags....this would be artificially false low).

There are other similar ideas out there on this site but I would like to see the ability to skip numbers in the Digital States Enumeration. We have areas of the plant that have states which don't map well to a 1,2,3.... set of states. Some are bit settings and others are just high numbers. Let users skip numbers and enter what they want (100,200,300, etc.) Numbers that aren't defined will be filled in by the system as "undefined" or something similar when shown in vision. It's difficult to create a set with 250 values and doesn't need to require a user to individually create a lot of "blank" values to get to the one you really want (I know you can import too but still).