microsoft / microsoft/powerplatform-vscode

pac modelbuilder - Use DisplayName for BPFs

Open
#508 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
277
Forks
60
Avg merge
1d 1h
Merged PRs (30d)
14

Description

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
https://github.com/daryllabar/DLaB.Xrm.XrmToolBoxTools/commit/bc5b43b0105b4aac5ec06c1057186ef48a3ec1d8#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:
https://github.com/daryllabar/DLaB.Xrm.XrmToolBoxTools/commit/4dfd96164b0626947bd07eb5017b01c2d4bfd9e2#diff-64f3542665f7570012cb548d669a5aa4593bb81515364f402cc8156fa88cec81 (look at GetNameForRelationship method)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Locate the PAC ModelBuilder naming-service or BPF model-generation entry point, then compare its behavior with the referenced GetNameForEntity and GetNameForRelationship examples. Done means BPF names use DisplayName values, append a GUID only for duplicates, and relationship names follow the intended naming behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
devtools
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.