Custom Connector for HMRC VAT Number Validation

-
I was scrolling through available API's on HMRC website and noticed this one which is in BETA:


This information would be very useful in PowerApps and also F&O, so I decided to create a custom connector around this API.

To do this I went to custom connectors section in PowerApps:


Then I clicked on New Custom Connector > Create from Blank.


I filled in the image, Host URL and clicked Security.


As this is an Open API and there is no security requirement, I just left this as is and went to the definition tab:


I filled in the various pieces of information here:


Then Clicked on new to create a new action for the first of the 2 available API's which is just to receive the VAT number without a reference number and then clicked on Import from Sample:


Checking the HMRC documents, this is a GET, so mark as GET and then I put in the URL, the URL is a combination of the Host URL and this end point /organisations/vat/check-vat-number/lookup/{targetVrn} when the Target VRN represents the VAT Reg Number you want to retrieve:




This should then create the input parameter you have in PowerAuomate like below:



For the response I put a sample URL in postman HTTP request and it returned the flowing, these will become the output of your step in PowerAutomate:


You can then test it:


Then you should get a response like below:


That's all for now, I will show you next how to use this connector within F&O to validate VAT Numbers.










 

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 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

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