Data entity for bank statement attachments

(4) Share

Report

Posted on by Viswanath M

128

Hi everyone,

I have created a custom entity to import document attachments for bank statements. However, when I try to import data using the Data Management Framework (DMF) or through a Power Automate flow, I receive the following error:"Field 'Reference record ID' must be filled in.; Warning: validateWrite failed on data source 'DocuRef (DocuRef)'."

I have referred to this Solved: Data entity for worker attachments - post and tried to skip data methods but still the issue persists. I also refer these inbuilt entities CustomerAttachmentsV2Entity, HcmWorkerAttachmentsEntity, SalesOrderHeaderDocumentAttachmentV2Entity and LedgerJournalAttachmentsEntity.

Categories:

Dynamics 365 Finance

Dynamics 365 Project Operations

Microsoft Dynamics AX

I have the same question (0)

All responses (7)

Answers (1)

Martin Dráb 237,990 Most Valuable Professional on at

Like (0)

Report

There are quite a few things to check. For example, are you using Inner Join to join BankStmtISOAccountStatement?

Was this reply helpful? Yes No
Viswanath M 128 on at

Like (0)

Report

Yes,

Was this reply helpful? Yes No
André Arnaud de Cal... 301,210 Super User 2025 Season 2 on at

Like (0)

Report

Hi Viswanath,

Have you added the fields RefTableId, RefRecId, and RefCompanyId on the field list of the data entity? If so, try to remove them or set these fields as non-mandatory for the data entity and staging table.

Was this reply helpful? Yes No
Viswanath M 128 on at

Like (0)

Report

No, I didn't add those fields to the entity.

Was this reply helpful? Yes No
Subhad365 21 User Group Leader on at

Like (0)

Report

Additionally you can take a look at the PURCHASEORDERHEADERDOCUMENTATTACHMENTENTITY - it makes a relation to PurchPurchaseorderHeaderV2Entity and doesn't have any refenrece to RefTableId, RefrecId or RefCompanyId. You too can follow a similar flow of the structure.

I called this entity from a flow, which succesfully attached the incoming file stream to the target PO:

Regards,

Subha

Was this reply helpful? Yes No
Viswanath M 128 on at

Like (0)

Report

I have seen this entity which is similar to the SalesOrderHeaderDocumentAttachmentV2Entity. Both sale and purchase document entity don't have RefTableId, RefrecId or RefCompanyId entity fields but, had the relationship to these fields. I have also tired replicate this entity for bank statement, but it also throws the same error.

Was this reply helpful? Yes No
Verified answer

Viswanath M 128 on at

Like (0)

Report

The error is solved after skipping validation & set the table buffer on mapEntityToDataSource method in data entity.

public void mapEntityToDataSource(DataEntityRuntimeContext _entityCtx, DataEntityDataSourceRuntimeContext _dataSourceCtx)
{
BankStmtISOAccountStatement bankStmtISOAccountStatement;

select firstonly * from bankStmtISOAccountStatement where bankStmtISOAccountStatement.Identification == this.Identification;

if(_entityCtx.getDatabaseOperation() == DataEntityDatabaseOperation::Insert && _dataSourceCtx.name() == tableStr(DocuRefEntity))
{
_dataSourceCtx.skipValidateWrite(true);
}

if (_dataSourceCtx.name() == dataEntityDataSourceStr(YS_BankStatementDocumentEntity, BankStmtISOAccountStatement))
{
_dataSourceCtx.setBuffer(bankStmtISOAccountStatement);
}

super(_entityCtx, _dataSourceCtx);

}

Was this reply helpful? Yes No