Electronic Reporting Payment File drops files locally

-

I thought I would post about this as I see some misleading information out there. When you generate a payment file from D365 F&O which has been set-up with Electronic Reporting you might get the payment file sent to the destination and also drop some files locally. 

I have found that unless you implicitly define a destination for a component it will drop the file locally, this includes the folders, so I have found even if you don't use it is best to include it in the destinations and just don't define a location for it.

The example below for UK(BACS) file shows how it can be set-up if you don't want to generate any files on payment.


I have personally found it best if you are taking a Microsoft configuration as a base to recreate the configuration and remove the components you don't need, then you can be a lot more selective around what is generated and how it is controlled.






Comments

Post a Comment

Popular posts from this blog

"Exception while trying to get Virtual Entity metadata for entity" Error on Data Events

-
Image
When enabling data events in D365 F&O you might get some error which says similar to below: Exception while trying to get Virtual Entity metadata for entity: ##### I checked the logs and the following is showing depth is "Basic, BusinessUnitId" Response status code does not indicate success: 403 ({"error":{"code":"0x80040220","message":"SecLib::CheckPrivilege failed. User: #### , PrivilegeName: prvReadEntity, PrivilegeId: #### , Required Depth: Basic, BusinessUnitId: #### , MetadataCache Privileges Count: 5803, User Privileges Count: 82"}}). This means to resolve this make sure your application user in PowerPlatform admin center has the Basic user role.
Read more

Electronic Reporting Bank Statement Import parsing account number for BAI2.

-
  When you import bank statements into D365 F&O using electronic reporting the system uses the account number field on the bank master to identify the bank account which should be used to create the statement. The BAI2 format contains the account identifier on the line starting "03", often this number is a combination of both the account number and another identification number the bank uses like sort code in the UK or BSB in Australia. In D365 F&O we have 2 separate fields to store this information and to get the standard import to work you have to include the full account identifier in the account number field, which may not be correct based on the locality. If you need to parse this number its possible by making a change to the model mapping on the format, just do the follow: 1. First create a custom format based on the standard format, against your configuration provider. 2. Go into designer on your custom format. 3. Go into Map Format to Model. 4. Go into Designe...
Read more

Electronic Reporting displaying Legal Entity Email/Phone by custom Address Purpose

-
 You may need different email addresses to display on outgoing business documents depending on department sending them or have different "from" email addresses for email's in the ER destinations. This can be done using a custom address purpose, in  the example below I created an Address Purpose called "AP" under  Organization administration > Global address book> Address and contact information purpose and gave it a purpose of contact. Then I added a email address to legal entity using this purpose. Then in the format add the following Class = DirParty Enumeration = LogisticsElectronicAddressMethodType Table = CompanyInfo Then add the following where you want to display the email address: DirParty.electronicAddressLocatorsByRole(CompanyInfo.'current()',LogisticsElectronicAddressMethodType.Email,"AP").
Read more