Skip to content

Commit 2ca6705

Browse files
committed
update docs
1 parent 5a82a87 commit 2ca6705

File tree

1 file changed

+2
-10
lines changed

1 file changed

+2
-10
lines changed

powerapps-docs/cards/manage-cards/manage-cards.md

Lines changed: 2 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -88,14 +88,6 @@ When importing a solution containing a card that depends on tables not present i
8888

8989
Instead, to identify which cards depend on which tables when resolving dependency issues, start by opening the card designer. Next, navigate to Cards from the sidebar, select the card you're interested in, and select Edit. Once the card designer opens, select Data from the sidebar to view the tables that card depends on.
9090

91-
### Card dependencies for flows aren't displayed correctly in solution explorer
91+
### Card dependencies for flows aren't represented in solution explorer
9292

93-
When importing a solution containing a flow that depends on cards not present in the same solution, the import fails if those cards aren't already present in the target environment. Similarly, removing a solution containing cards that a flow depends on fails. The dependency viewer in these scenarios is not helpful at identifying which tables or cards is causing the operation to fail.
94-
95-
Instead, to identify which cards depend on which tables when resolving dependency issues, start by opening the flow editor. Next, find actions for the Cards for Power Apps connector. For each of these actions, identify which card is referenced.
96-
97-
### Solutions with flows depending on cards and tables may not be importable if the card and table is removed
98-
99-
In the scenario that you create a flow inside a solution, which depends on a card, which in turn depends on one or more tables in the current environment, if you update your flow to no longer depend on the card and remove that card and the required tables from the solution, you will not be able to import the solution to any environment due to missing dependencies.
100-
101-
To work around this issue, you can create a new solution and add the flow directly to that solution. Exporting and importing this new solution works.
93+
When importing a solution containing a flow that depends on cards not present in the same solution, dependencies on cards will not be enforced. The solution maker must ensure that cards used in the flow are also present in the solution or the target environment to ensure the flow works correctly in the target environment.

0 commit comments

Comments
 (0)