Unable to import into child tables correctly

[ncunningham9]

Type of Connector

Certified Connector

Name of Connector

Dynamics 365 Business Central

Describe the bug

Using the D365BC Connector inside Power Automate, users are unable to import into a "child" table while referencing the "parent" table, because the parent table name is a primary key inside the child table. Primary Keys cannot be imported into, but that is a requirement for basic functionality of child tables.

We can create a flow that imports into child tables without primary keys. In this instance, standard users wouldn't ever be able to find the appropriate records. The below examples are for Price Lists. We imported into the Price List table but the Price List Code field is blank, making that record meaningless.

Is this a security bug?

No, this is not a security bug

What is the severity of this bug?

Severity 2 - One or more important connector features are down

To Reproduce

1. Create a custom API for a "child" table. Examples: Price List Lines, Production BOM Lines, or Routing Lines.
2. Go to Power Automate
3. Create a Flow and add an action with the D365BC Connector
4. Select "Create a Record"
5. Click Advanced Parameters and scroll through the list of available fields.

Expected behavior

1. Create a custom API for a child table.
2. Power Automate Flows would allow a primary key through the Advanced Parameters menu (or, at least one main primary key in order to associate it with a parent record),
3. If the Primary Key is not imported into correctly, the flow would fail with an error message something like "Unknown Parent Record".

Environment summary

Install Method (e.g. pip, interactive script, apt-get, Docker, MSI, edge build)
CLI version (paconn --version)
OS version
Shell Type (e.g. bash, cmd.exe, Bash on Windows)

I'm not sure of any of the above. I'm using standard cloud-based Power Automate Flows.

Additional context

These are the tables that I'd like to insert into, but because of this issue, cannot.
Price Lists
Production BOM
Routings
We are forced to create an excel-based automation that users can then import into configuration packages.