I'd like to apologize in advance if my question is very generic or obvious.
I was given a task to build application that will check, based on provided inputs and connection/relationship schema, the validity of the records. I have documents which are in relationship with other doc, once new/revised document is uploaded I'd like to see the relationship and the overall impact and address those changes on the other documents. As example see below diagram:
Documents #1 are in relationship with Applicable documents #2. But sometimes Document from group #1 may refer to another document from group #1. Whenever new revision of document #1 or document #2 is issued, I'd like to see all documents which need to be revised/updated.
My questions is what database would you prefer to use to point those changes?
@espan88 From your scenario, you need a database that can handle Many-to-Many relationships graciously.
Dataverse is a data platform that's baked into the Power Platform. It's more than a database as it handles lot of things like security, scalability etc., automatically.
Dataverse handles Many-to-Many relationships very well and also hides much of the complexity.
I would suggest to get a basic schema sketched out and then start putting in your relationships.
Hope this intro helps!
@espan88M-to-M is quiet simple in Dataverse, the data platform that comes along with the Power Platform. If you have some thing more concrete, let me know and we could try and build it.
@CNT As of now, I don't know where I should start 😐. I'd like to start with raw data, so it can be imported to DB but i don't know how to construct input files. If Doc#1 list with names and revision numbers in one table and for Doc#2 same? Build the relation?
Doc#1 (A) -> Doc#2 (A)
-> Doc#2 (B)
-> Doc#2 (C)