microsoft / microsoft/Dynamics-365-FastTrack-Implementation-Assets

Add CRM tables as an option

Open
#392 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Jupyter Notebook
Stars
494
Forks
296
Avg merge
1d 10h
Merged PRs (30d)
5

Description

As a suggestion, CRM tables follow a similar format coming from Fabric Link with IsDelete, Enum values, and the same issue with case sensitivity in the lakehouse.

Would like to see an option to add CRM only with the option that gets FnO tables or all tables.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue mentions CRM tables, FnO tables, Fabric Link, and lakehouse case sensitivity, but it names no files or tests. Start by locating the existing option that adds FnO tables and determine where table selection and case handling are implemented; done means CRM-only and all-table choices behave consistently.

Written by the indexing model from the issue text.

Assessment

Domain
databases
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.