microsoft / microsoft/Dynamics-365-FastTrack-Implementation-Assets
MergeData step does not retrieve data when db schema is passed with table name
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 494
- Forks
- 296
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 5
Description
The MergeData step in the IncrementalExport_SQL pipeline is not able to handle the parameter @TargetTable to contain the database schema. When the schema is passed into this step, the select statement which fills the @UpdateColumns value does not find any columns.
Problem is, that the @TargetTable ist used to filter in the TABLE_NAME column, where the schema is not part of the name.
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 in the MergeData step of the IncrementalExport_SQL pipeline and inspect the select statement that fills @UpdateColumns. Trace how @TargetTable is compared with TABLE_NAME when it includes a schema, then verify the fix with a schema-qualified table name and confirm that the update columns are retrieved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100