You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By default, the naming service for bpfs uses the logical names, not the display names. This generates some extremely hard to read names in the format Publisher_bpf_GUID. The Display Name should be used instead (and the GUID can be added if there is a duplicate name)
By default, the naming service for bpfs uses the logical names, not the display names. This generates some extremely hard to read names in the format
Publisher_bpf_GUID
. The Display Name should be used instead (and the GUID can be added if there is a duplicate name)If it's helpful, I've added code to my naming service to resolve this in the EarlyBound Generator
daryllabar/DLaB.Xrm.XrmToolBoxTools@bc5b43b#diff-64f3542665f7570012cb548d669a5aa4593bb81515364f402cc8156fa88cec81 (look at the GetNameForEntity method particularly, although I'm assuming that there is a better way to determine that the entity name is for a BPF entity)
Also for relationship names:
daryllabar/DLaB.Xrm.XrmToolBoxTools@4dfd961#diff-64f3542665f7570012cb548d669a5aa4593bb81515364f402cc8156fa88cec81 (look at GetNameForRelationship method)
The text was updated successfully, but these errors were encountered: