Release notes Kiwa

Trust
Quality
Progress
Scope of this Release
Replace D365FO connector with HTTP connector
Replace D365CE Dynamics connector with Data verse connector

2
Replace D365FO connector with HTTP connector
What is the change about?
We make use of D365FO connector in Logic Apps while integrating with D365FO. These connectors
have number of issues and we have found that HTTP connector is better performant.

HTTPS Dynamics connector

Performance is much better (~8x faster). This because it makes a direct

Performance is poor. The call goes via custom connector, then to D365FO
connection D365FO environment

It supports Cross company queries It does not support cross company queries

Less probability throttling exception. The throttling exception is limited to

More probability throttling exception. The throttling exception is limited to D365FO
D365FO

Supports App and Managed identity-based authentication (more secure) It does not Supports App and Managed identity-based authentication (more secure)

Nesting of queries (Expand) is supported, resulting in lesser actions. As a Nesting of queries (Expand) is not supported, resulting in lesser actions. As a result, expensive
result, cheaper and faster execution of Logic App and slower execution of Logic App

No impact on Microsoft changes to dynamics connector The integration could break due to changes done by Microsoft

The development time is higher and requires more technical skills. This connector helps developer and reduce the development time

3
Replace D365FO connector with HTTP connector

What is the business requirement?

NA
What is the business value?
The integration will be more secure and high-performance integrations.
Who are the intended users?
NA
Design Documentation
CP Accounts:
Ecert Accounts:
IDD Hours:
Sales Order:
4
Replace D365FO connector with HTTP connector

Testing and testcases

Sales Order Integration (CE-FO/Ecert)
Hours Integration (Ecert – FO)
CP-FO integration (Sales Order)

5
Replace D365CE connector with Data Verse
What is the change about?
The classic Dynamics connector used in current Azure integration, are being deprecated by Microsoft.
These connectors needs to be replaced with new DataVerse connectors. These connectors are the
Modern way to interact with CE and FO from Azure Integration
Dynamics 365 Connector is deprecated

Effective May 5, 2020 the Dynamics 365 connector used for Flows, Logic Apps, and Canvas Apps is officially deprecated. We recommend that you do not create new

connections using this connector.Rather than use the Dynamics 365 connector, the Common Data Service (Current Environment) connector should be your first

choice if you can use it. You may not be able to use the Common Data Service (Current Environment) connector in every situation today because of the following

limitations:

• It is not available in Logic Apps.

• It does not enable cross-tenant or cross environment connections.

• It cannot be used for canvas apps that use the Power Apps for Windows client.

6
Replace D365CE connector with Data Verse

What is the business requirement?

NA
What is the business value?
The integration will be future proof.
Who are the intended users?
NA
Design Documentation
CP Accounts:
Ecert Accounts:
IDD Hours:
Sales Order:

7
Replace D365CE connector with Data Verse

Testing and testcases

Account Integration
CE-ECERT Contract Line integration
CE-CP Contract Line integration
CE – FO Sales order Integration

8
General step by step plan
1. Drafting release notes  (this document)
2. Drawing up a delivery scenario (draaiboek) DTAP
3. Installation CNS01 environment
4. Installation TST01 environment
5. Test HSO TST01 environment
6. Refresh ACC01 environment
7. Installation ACC01 environment
8. Test Kiwa ACC01 environment
9. Acceptance and accord delivery to PROD

9
Templates sheets release notes

Trust
Quality
Progress
Logic App changes for HTTP connector

US15050: This user story responsible for replacing sales order integration with Dynamics
CE connector and Dynamics FO connector

US15039: This user story responsible for replacing Account integration with Dynamics CE
connector with Data Verse connector

US15048:This user story responsible for replacing Hours integration with Dynamics CE
connector and Dynamics FO connector

US15049:This user story responsible for replacing projects integration with Dynamics CE
connector with data verse connector

11 [brand name]
Change US15049:
Description of the change (including a link to a FFD or
IDD or ….) including reference number (DevOps)
Which applicates are involved?
Impact on the (part)solution
Test scenarios
consistency with other adaptations
Points of attention for (integral) testing by Kiwa
Method of implementation in PROD, including what
should be done before installation and what should be deployment
done after installation? Which (extra) setup is needed,
etc.
Order of installation during delivery in PROD, in
conjunction with other adjustments to be delivered.
Advice for support, monitoring needed? control
moments in time maybe, etc.
12
US15049: The user story is responsible for implementing CP specific integration for
Project records from D365CE. When a Project record has been created or changed in CE,
the information related to the Project Record is sent to Azure Service Bus. This story
is responsible to pick up the message and send it to CP system
IDD Sales agreements D3565CE-CP​
TD CP Integration
D365CE, CP
None
Test cases
Performance
Automatic Deployment using Azure DevOps. The connections should be authenticated post
NA
Logic Apps needs to be added to MS Monitoring
Change US15050:
Description of the change (including a link to a FFD or
IDD or ….) including reference number (DevOps)
US15050: The user story is responsible for implementing integration for Project Contract Line
record in D365CE. When a Project Contract Line record has been created or changed in CE, the
information related to the Project Contract Line Record is sent to Azure Service Bus
IDD Sales agreements D3565CE

Which applicates are involved? D365CE, ECERT, CP

Impact on the (part)solution None
Test scenarios Test cases

consistency with other adaptations

Points of attention for (integral) testing by Kiwa Performance
Method of implementation in PROD, including what Automatic Deployment using Azure DevOps. The connections should be authenticated post
should be done before installation and what should be deployment
done after installation? Which (extra) setup is needed,
etc.
Order of installation during delivery in PROD, in NA
conjunction with other adjustments to be delivered.

Advice for support, monitoring needed? control Logic Apps needs to be added to MS Monitoring
moments in time maybe, etc.

13
Change US15039 :
Description of the change (including a link to a FFD or US15039: The user story is responsible for implementing integration for Account record in
IDD or ….) including reference number (DevOps) D365CE. When an Account record has been created or changed in CE, the information related to
the Account Record is sent to Azure Service Bus and then the targeting application such as
ECERT and CP
CP Accounts:
Ecert Accounts:
Which applicates are involved? D365CE, CP, ECERT
Impact on the (part)solution None
Test scenarios Test cases

consistency with other adaptations

Points of attention for (integral) testing by Kiwa Performance
Method of implementation in PROD, including what Automatic Deployment using Azure DevOps. The connections should be authenticated post
should be done before installation and what should be deployment
done after installation? Which (extra) setup is needed,
etc.
Order of installation during delivery in PROD, in NA
conjunction with other adjustments to be delivered.
Advice for support, monitoring needed? control Logic Apps needs to be added to MS Monitoring
moments in time maybe, etc.

14
Change US15048 :
Description of the change (including a link to a FFD or US15039: The user story is responsible for implementing integration for Time registration
IDD or ….) including reference number (DevOps) information in ECERT to FO. When a time registration record has been created or changed in
ECERT, the information related to the Time registration Record is sent to Azure Service Bus and
then the targeting application D365FO
IDD Hours:

Which applicates are involved? D365FO, ECERT

Impact on the (part)solution None
Test scenarios Test cases

consistency with other adaptations

Points of attention for (integral) testing by Kiwa Performance
Method of implementation in PROD, including what Automatic Deployment using Azure DevOps. The connections should be authenticated post
should be done before installation and what should be deployment
done after installation? Which (extra) setup is needed,
etc.
Order of installation during delivery in PROD, in NA
conjunction with other adjustments to be delivered.

Advice for support, monitoring needed? control Logic Apps needs to be added to MS Monitoring
moments in time maybe, etc.

15