Custom Connector for VIES for European Vat Number validation.

-

 As companion piece to my custom connector blog for HMRC:

Custom Connector for HMRC VAT Number Validation | D365 F&O | Power Platform (alexdobinson.blogspot.com)

I wanted to do the same thing for European VAT numbers via VIES API which is documented here:

https://ec.europa.eu/taxation_customs/vies/technicalInformation.html

First thing to be aware with the API to get the WSDL file from here:

https://ec.europa.eu/taxation_customs/vies/checkVatService.wsdl 

In a chromium browser use the save page as:



Then save it as a WSDL file:



We can use Postman, go to File > Import


Then select WSDL:


I made adjustments to the collection that was created, by adding 2 variables here.




Do some testing you can find the different formats based on country on vies website, then I loaded as a customer connector using a postman collection which is detailed here.

Create a custom connector from a Postman collection | Microsoft Docs

When I tested I used a raw body same defined in postman.


Thats all for now.








 

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