Skip to content

Clarify ComponentType guidance for solution components#2870

Open
Sarthak-Agrawal wants to merge 1 commit intoMicrosoftDocs:mainfrom
Sarthak-Agrawal:clarify-addsolutioncomponent-componenttype
Open

Clarify ComponentType guidance for solution components#2870
Sarthak-Agrawal wants to merge 1 commit intoMicrosoftDocs:mainfrom
Sarthak-Agrawal:clarify-addsolutioncomponent-componenttype

Conversation

@Sarthak-Agrawal
Copy link
Copy Markdown

Adds guidance before the AddSolutionComponentRequest sample explaining when to use ComponentType values, where common values come from, and when to prefer creating or updating the component in the target solution context with SolutionUniqueName.\n\nThis aligns the conceptual article with the more current guidance in the AddSolutionComponentRequest reference remarks.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@learn-build-service-prod
Copy link
Copy Markdown
Contributor

Learn Build status updates of commit ccc656b:

✅ Validation status: passed

File Status Preview URL Details
power-platform/alm/solution-api.md ✅Succeeded

For more details, please refer to the build report.

Copy link
Copy Markdown
Member

@phecke phecke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Sarthak-Agrawal I have approved the PR. However, we always work in the private (-pr) repos - for example, power-platform-pr. After merging this PR, I will have to migrate the change to the private repo before the update can be published. Please keep this in mind the next time you work in our Learn repos.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants