Currently, if an attempt is made to use a name that is already used within a scope, a red toast appears that states:
"[ObjectName] is already taken by another object”.

However, this does not help the user in identifying where that name is used, and can present complications if the user wants to rename the original name to allow the desired name to be used in the new Object.

The proposal involves changing the formatting of the text in the red toast popup to give a more precise hint as to where the name is already used:

Instead of: "[ObjectName] is already taken by another object”

Moving to: " [ObjectName] is already taken by another [ObjectType]”
Eg: " [ObjectName] is already taken by a Trigger”

Repro Steps:

1) Create a Studio Project featuring a MainPage.xaml

2) Rename the root Grid to "MyTest"

3) Introduce another Element into the rootGrid, and once placed, rename it to "MyTest".
Observe a red toast notification appearing indicating the name can't be used, because it is already employed, but does not indicate that it is used by another Element.

4) Navigate to the Interactivity/Triggers Panel, and create a new DataEvent Trigger on the root Grid.

5) Rename the [DataTrigger] in the Interactivity/Triggers Panel to "MyTest"
Observe a red toast notification appearing indicating the name can't be used, because it is already employed, but does not indicate that it is used by another Element.

6) Create a new Action inside of the Data Trigger created in Step 4), and rename the new Action to "MyTest"
Observe a red toast notification appearing indicating the name can't be used, because it is already employed, but does not indicate that it is used by another Element.

Expected Results: Toasts warning the user of an invalid name due to being a duplicate, give further hints as to where the name is already used, to help the user trace it down to change it if desired.