Skip to main content

Entities

This document describes all entity related information for Eftsure inside D365 F&O. Please see the following links for more information on how to use entities and connect third party utilities for development.

Open Data Protocol (OData) - Finance & Operations | Dynamics 365 | Microsoft Learn

Test services by using third-party utilities - Finance & Operations | Dynamics 365 | Microsoft Learn

Entities

This extension is shipped with several data entities in order help accessing Eftsure data outside of Dynamics. The below artifacts are available to be consumed by any OData client, including LogicApps, Flow, Postman, ...

Configuration

This subset of entities is used internally to import export configuration to file/cloud, across environments for any project purposes.

Archiving configuration locally or to the cloud for later availability is recommended after each config change.

info

Eftsure credentials and connection details are not persisted as part of these entities into order to avoid confusion and invalid passwords after imports.

Project

This subset of entities is used internally to import export projects to file/cloud, across environments for any project purposes.

Archiving projects locally or to the cloud for later availability is recommended after each project change.

Main

These entities have been designed to help customers extract Eftsure data from Dynamics. All custom fields from vendors, bank accounts, onboardings are available for external use, but these entities are readonly and should only be updated from Eftsure cloud.

The following screen is available in Eftsure parameters to facilitate the use of Eftsure-related data entities:

Screenshot

For more information, please visit Data entities

This screen lists all new or extended entities in our extension:

  • For each entity, the field list is displayed alongside.
  • All Eftsure entities and fields are highlighted in gray.

This screen should facilitate the discovery of our entites.

Master data

Most Eftsure data should be available already, either at the vendor or bank account level using PESVendTable and PESVendBankAccountEntity.

Standard entities

  • CustCustomerV3Entity: Extended with GovCode information
  • VendVendorBankAccountEntity: Extended with main Eftsure information
  • VendVendorV2Entity: Extended with GovCode information

New entities

  • PESGovCodeEntity: Contains all government code data
  • PESOnboardingInfoEntity: Contains all onboarding header information
  • PESOnboardingFieldEntity: Contains all onboarding fields information including attachments.
  • PESVendTableEntity: Contains all vendor level Eftsure information
  • PESVendBankAccountEntity: Contains all bank account level Eftsure information
  • PESVendorHistoryLogEntity: Contains all historical changes recorded by our Vendor History feature.

Screenshot

Parameters

A number of entities are also available in the system to allow for importing/exporting your configuration, using Data Management.

For more information, please see Config Import and Config Export

warning

These entities are not likely to be used in an integration scenario.

More

warning

If a new entity or fields are required, please reach out to support for an extensibility/integration request.

Please find here some helpful references:

Querying or browsing an OData endpoint

Query/Filter syntax

Code Samples

Code examples for consuming OData are available in the Microsoft Dynamics AX Integration GitHub repository

Permissions

The entities described in this document are controlled via standard security privileges

Screenshot

To customise Eftsure security, please use System Administration > Security configuration tool.

For more information, please visit:

Role based security

Import Export customized security

The screenshot below shows customisation of Eftsure permissions for a specific role/duty/privilege.

Screenshot