microsoft / microsoft/Dynamics-365-FastTrack-Implementation-Assets
New Custom Fields Missing from tables
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 494
- Forks
- 296
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 5
Description
Hello,
I created the DVLinkToSQL_Incremental_Copy pipeline and it works fine.
However, I notice that new custom fields added in F&O are not added from Dataverse to my dedicated SQL pool.
To view new custom fields in SQL, I have to put a new schema name in the schema parameter and then I see them.
But then I have a new set of tables in my SQL Pool.
Is there a way to add new custom fields in SQL Pool without running the pipeline with a new schema?
Any help is appreciated.
Thanks!
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
No files, tests, or implementation entry points are named. Start by reviewing the DVLinkToSQL_Incremental_Copy pipeline and its schema parameter, then trace how Dataverse custom fields are selected and mapped into the dedicated SQL pool. Done means determining whether existing tables can receive newly added fields without creating a new schema, and documenting or implementing the supported behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- data-engineering, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100