Connector Improvement: Unable to select only one child table from EntraID schema
CompletedHi Team,
I hope this email finds you well. I am reaching out to seek your assistance regarding an issue we are facing with our EntraID data ingestion process. Specifically, we only need a few columns from the User table, but due to schema constraints in Fivetran, we are forced to ingest the primary keys (PKs) from all the child tables. This has resulted in increased sync time and a higher number of rows than necessary.
I’ve raised this with Fivetran support (Ticket 323129) and they advised me to raise a feature request as right now, the EntraID Lite connector treats each parent object (like USERS or GROUPS) together with its child objects as one combined structure. Because the child data is fetched inside the same API call, the connector can’t turn individual child tables on or off — they inherit the parent’s state. This is why those child tables appear greyed out in the Schema tab.
Could you please prioritise the feature request as the sync is loading a lot of data which are not at all required, slowing down the sync process, causing sync failure due to an internal Out of Memory (OOM) error, increase in data consumption, etc.
Thank you for your time and support. Looking forward to your prompt response.
Best regards,
Sandeep.Pushpan
-
Official comment
Hi Sandeep,
We are actively working on this feature, and this capability will soon be available for the connector.Thanks,
Unni
Please sign in to leave a comment.
Comments
1 comment