-
Notifications
You must be signed in to change notification settings - Fork 100
Open
Labels
Fix rolling outWe start the rollout with the fix for this issue.We start the rollout with the fix for this issue.bugSomething isn't workingSomething isn't working
Description
Describe the bug
The pac code list-connection-reference -s <solutionId> command fails.
Steps to Reproduce
- Add at least one connection reference into a solution (e.g. Office 365 Outlook)
- Create an auth profile in pac CLI with a user that has system admin / global admin
- Run the command
pac code list-connection-reference -s 952a1bd3-24d7-42c3-a44b-61bac7cfc35f - See error
Expected behavior
The list of connection references in the target solution to be outputted in the terminal.
Actual behavior
A TypeError is returned.
Screenshots or Error Messages
Error during CLI execution: TypeError: Cannot read properties of undefined (reading 'trackScenario')
Environment information
- PAC CLI Version: 2.4.1+g3799f3e (.NET Framework 4.8.9221.0)
- Office 365 Outlook connection reference exists in a solution
Additional context
The Dataverse web API doesn't correctly return the expected connection references. I observed the following:
- The
/api/data/v9.0/connectionreferences?$select=connectionreferenceid,solutionid,connectionid,connectionreferencelogicalnamequery shows the connection reference in the default solution, rather than my custom solution. I published all customizations in the solution to see if that helps but it made no difference. - The query
api/data/v9.0/connectionreferences?$filter=solutionid eq 952a1bd3-24d7-42c3-a44b-61bac7cfc35freturns an empty array for both default solution that the previous query reported the conn reference is in, and also for the solution that it is in.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Fix rolling outWe start the rollout with the fix for this issue.We start the rollout with the fix for this issue.bugSomething isn't workingSomething isn't working