Working for multiple D365 instances ->OnPremise & Cloud

(0) Share

Report

Posted on by MaSc4Crm

Hi guys,

we are planning to have multiple Online D365 (Sales) instances across the world. Some instances needs to be OnPremise.

Is there any best practices* to develop for Cloud and OnPremise at the same time - I would like to reduce to minimize the effort.

* E.g. separating solutions in a special way to guarantee deployment readiness? I'm working with CRM since over 10 years, but this requirement is quite new for myself.

Regards,

Martin

I have the same question (0)

All responses (9)

Answers (1)

Suggested answer

Wahaj Rashid 11,321 on at

Like (1)

Report
Hi,

Thank you for your query.

When you are creating to customize a component, make sure it is compatible with the online version (not vice versa).

For example, you can do the following on an on-premise instance:

SSRS Reports using SQL Server Queries (T-SQL instead of FetchXML).

Plugin Assemblies registered on disk.

However, both of the above will not work in an Online Environment.

In summary, I follow best practices considering it should support online as well (if we ever upgrade).

For the solutions and their components, I will make sure:

Reports created using Report Wizard or Fetch XML (SSRS).

Plugins are registered in Isolation Mode.

Make sure 3rd-party APIs are being accessed using a named URL (so it works in an online environment as well).

Apart from custom solutions, keep an eye on the features (being utilized by your solutions). Because most of the new features are introduced in the Online version first (and later on an on-premise environment).

If you follow these above practices, you should not find any issues and your solutions should work in both Online and On-premise environments.

Was this reply helpful? Yes No
MaSc4Crm 6 on at

Like (0)

Report

Hi Wahaj,

thanks for your reply.

As a Solution Architect I has been dealing only with cloud or onpremise D365 within a project.

Both at the same time is now my challenge - to find a way to handle development in a pragmatic way.

My solution currently is to setup two separate dev streams, this means in the end more effort

Regards,

Martin

Was this reply helpful? Yes No
AriaConsulting 2 on at

Like (0)

Report

MaSc4Crm, as Wahaj Rashid said, you don't need, and really should not have, 2 dev streams. Have 1 stream that focuses on ensuring whatever is built/configured works for D365 cloud and that should essentially gaurantee compatability with on-prem.

Was this reply helpful? Yes No
MaSc4Crm 6 on at

Like (0)

Report

Hi guys,

how do we guarantee that the solutions are compatible on on premise and on cloud versions? I mean, there was this compatible table for solutions versions

https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/introduction-solutions?view=op-9-1

Is there any update?

I'n my opinion, we need to develop on a on premise CRM to guarantee the compatibility with cloud. Then we can have just one dev stream.

What do you think?

Was this reply helpful? Yes No
Verified answer

AriaConsulting 2 on at

Like (0)

Report

As Wahaj and I said, if you target your dev at being compatible with cloud then the very large majority of the time it will be compatible with on-prem. MS focuses everything at the 365 stream for the Dynamics business unit and then follows up with on-prem releases. There may be very occasional situations where your design that works fine in 365 creates errors in on-prem. Usually that is because you happen to be doing something that MS forgot to include i the release to on-prem. But managing 2 design, dev, test, and deploy streams for those rarer occasions is highly wasteful of cost and resources.

Was this reply helpful? Yes No
MaSc4Crm 6 on at

Like (0)

Report

Hi guys,

would do you recommend for having on premise and cloud versions of CRM and to reduce implementation/maintaining effort?

Is the best way to develop everything with on premise instance in order to guarantee the import to cloud version? Related to answer of Lorne, this describes the opposite way -> From cloud to on premise.

Regards,

Martin

Was this reply helpful? Yes No
Suggested answer

Wahaj Rashid 11,321 on at

Like (0)

Report

Hi,

That depends on what kind of options you have, in my opinion, if you have an online subscription, build your solutions Online (to make sure it is compatible on both online and on-premise).

Was this reply helpful? Yes No
MaSc4Crm 6 on at

Like (0)

Report
Hi Wahaj,

the problem is, that I can't use a cloud D365 instance as a dev environment - even if I segment my components correctly, because I can't import the solution to onpremise due this FACT:

support.microsoft.com/.../-you-can-only-import-solutions-with-a-package-version-of-9-0-or-earlier-into-this-organization-error-occurs-in-dynamics-365-59f8d360-d9ac-4354-f428-9a12ef2a811f

There are two options in my opinion:

Use onpremise DEV as source

Establish two separate dev streams (Cloud and onpremise)

I don't want to use either for these options - any suggestions?

Regards,

Martin

Was this reply helpful? Yes No
Wahaj Rashid 11,321 on at

Like (1)

Report

a33ik, what's your take on this?

Was this reply helpful? Yes No