microsoft / microsoft/Dynamics-365-FastTrack-Implementation-Assets
Inherited Tables when using EntityUtil to generate data entities as views in Fabric
Open
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 494
- Forks
- 296
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 5
Description
Hi
These are questions more than issues, but I don't know where else to ask them:
- Given a list of data entities, how do I know which inherited tables are required?
- Is it ever necessary to regenerate the tableinheritance.json file, and, if yes, how?
- Does the answer to point 2 above change if there is an ISV product which has it's own data entities which also need to be created as views in Fabric?
Thank you
Peter
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the EntityUtil workflow and the tableinheritance.json file mentioned in the issue. Determine how inherited tables and ISV data entities are identified and documented; done means providing clear answers to all three questions, including when and how regeneration is required.
Written by the indexing model from the issue text.
Assessment
- Domain
- databases
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100