Answered

Using 2 tables to create 3rd table and editing it

(0) Share

Report

Posted on by Mariollo

I am currently working on an app but during this process I have a lot of ideas and questions so I'd like to ask you guys if it is possible to build an app this way in Power Apps like described below.

I have two tables (screen below):

TABLE 1 - INCIDENT TABLE
TABLE 2 - CRITERIA TABLE

They have matching column (TECHNOLOGY).

Screenshot 2022-01-28 120348.png

I am currently creating TABLE 3 by importing TABLE 1 and TABLE 2 to PowerBI, connecting this together and then creating a Sharepoint list.

But there is a lot of work within SP list to import this table.

In PBI I can create relationships and create TABLE 3 in few clicks. I wonder if it possible work like this in PowerApps and SharePoint List?

What more I'd like to have possibility of editing TABLE 3 and change all YES values to something like "OK" or "NOT OK" and save it back to Sharepoint List.

Categories:

Building Power Apps

All responses (5)

Answers (1)

Sort by

WarrenBelz 156,774 Most Valuable Professional on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @Mariollo ,

One of the first things you will learn about SharePoint is that it is not a Relational Database and it is certainly not SQL, however a bit of thought on your data structure will let you do most things you need to do. One of the things you should not plan however is "look through" queries such as the one you propose. I regularly "de-normalise" data so that there is only one (or no) "levels of query". Doing anything else has the potential of Delegation issues that you really do not need.

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

Visit my blog Practical Power Apps
Mariollo 96 on at

Like
a
(0)

Report
Copy link

Link copied!

Do you have any hints on this particular case?
I've been building this app already using the method I wrote but I have somewhere in my head impression that there is much better way to do this 🙂
Verified answer

WarrenBelz 156,774 Most Valuable Professional on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @Mariollo ,

I would have the Incidents and Criteria tables as one table with all the combinations.

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

Visit my blog Practical Power Apps
WarrenBelz 156,774 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @Mariollo ,

Just checking if you got the result you were looking for on this thread. Happy to help further if not.

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

Visit my blog Practical Power Apps
Mariollo 96 on at

Like
a
(0)

Report
Copy link

Link copied!

That is exactly what I have right now and from what you've told it's the best solution so I won't change it.
Thank you for your insight.