-
Notifications
You must be signed in to change notification settings - Fork 328
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New command: m365 pp pipeline list #6287
Comments
I would like to take on this task. Could you please assign it to me? Thank you! |
Sure thank you @DevPio! |
Is it acceptable for the response to return only the user ID in the Owner property? When retrieving pipelines, the response currently returns just the user’s ID instead of detailed information like fullname or firstname. Additionally, in the PR, it’s suggested to return the following data: Name However, expanding the Owner field consistently throws this error: "Could not find a property named 'fullname' on type 'Microsoft.Dynamics.CRM.principal'" To fetch the user's details, it seems a separate request would be needed for each user, which may not be efficient in terms of performance. Is it acceptable to continue returning only the user ID, or should additional user details be included in the response? |
@appieschot, do you know a way to make it work? If not, then we just keep the response as-is. |
@appieschot can we proceed with the standard API response? |
Yeah we can proceed with standard API repsonse! Let's get that one in first 🦾. Great job so far! |
Usage
m365 pp pipeline list
Description
List all pipelines in the specified Power Platform environment.
Options
-e, --environmentName <environmentName>
--asAdmin
Examples
List all pipeline models in the given Power Platform environment.
List pipeline models in the given environment as admin.
Default properties
Additional Info
You can have a look at the logic behind: https://learn.microsoft.com/en-us/power-platform/developer/cli/reference/pipeline and/or https://learn.microsoft.com/en-us/power-platform/developer/pipelines/table-reference
The text was updated successfully, but these errors were encountered: