Share
Report
382Hi All,
I'm finding the scenario below harder than I think it should be and I'm wondering if I'm missing something. Please weigh-in with any insights.
Assume two environments in the same tenant: DEV (unmanaged solution environment) and TEST (managed):
- Create and configure a new Application User for use in both environments - call it "SPN Flow Execution"
- In DEV, create a new unmanaged solution - call it "Demo Solution"
- Add a Flow to the solution - call it "Demo Flow"
- Trigger:
- "When a record is selected"
- Create a new SPN-based connection to Common Data Service - call it "DEV SPN CDS Connection"
- Account entity or whatever you like
- Action:
- "Create a new record"
- Create a new SPN-based connection to Common Data Service (current environment) - call it "DEV SPN CDS (current) Connection"
- Create a new Account and add static values for required fields
- Trigger:
- Add a Connection Reference (preview) to the solution - call it "Demo CDS Connection"
- Connector: Common Data Service
- Connection: DEV SPN CDS Connection
- Add another Connection Reference (preview) to the solution - call it "Demo CDS (current) Connection"
- Connector: Common Data Service (current environment)
- Connection: DEV SPN CDS (current) Connection
- Update Flow Trigger and Action to use appropriate Connection References
- Publish and export solution as managed
- Add a Flow to the solution - call it "Demo Flow"
In TEST, import solution and see where things start to break down...
When deploying to TEST:
The import process wants the user to associate the Connection References included in the solution with local connections. At this point, I would expect to be able to create a new connection using the SPN I setup in the environment, however, only user-based connections are displayed and only user-based connections can be created using the "+ New connection" button.
In a given environment, an admin is unable to create an SPN-based connection outside the context of a Flow. Prior to attempting a solution import I can't go into TEST, navigate to Data -> Connections -> "+ New connection" and create SPN-based connections that will then be associated with the Connection References.
Furthermore, I can't create a quick Flow in test to establish the two new environment-specific connections (e.g. "TEST SPN CDS Connection" and "TEST SPN CDS (current) Connection") and then go back to the solution import UI to refresh the list and choose one. Hitting refresh and they never show up.
Anyone from the engineering team that can shed some light on the expected deployment scenario here?
All responses (
Answers (
