Is it possible to export a solution from an online organization of Dynamics 365 (V9), and import it in an On-premise organization (V9), to get all customizations and configurations of the online version to the on-premise version ? Is there any limitation or restriction ?
Thanks in advance.
most of the Customization such as entities, Fields, Views and so on shall be ok to import On-premise but there can be few of the customization which will not work as On-Line is higher version than On-Prem. I would suggest you go increment i.e small package at first and then keep implementing it.
Refer to these Links for more understanding
Link 1
Link 2
Link 3
Related
Does anyone knows a way to map the dependencies or requirements of any GCP API?
E.g. enabling container.googleapis.com would automatically enable compute.googleapis.com and others into a same chart/table/text/anything.
The GCP docs don't specify any such dependency for any API (from what I have seen so far). So I'm either looking for a Doc which specifies this, a gcloud command or a completely different tool that can help mapping it.
We don't have any public external documentation around service dependencies for now. therefore please open a FR in refer to this link
did you open a Feature Request as suggested ? If so, can you share the link ?
As a faint consolation, you can have a look at this article from which we can tell that the API interdependency information was once available through the serviceusage API.
There you'll find a diagram as of october 2020 (see screenshot bellow)
One workaround could be to use the Service Usage API. The disable method has a disableDependentServices field which disables all services that depend on the services being disabled.
You could enable a bunch of services in GCP, disable a service, and observe which dependent services are also disabled.
I did end up opening a feature request for this and the fact that I had to do so still boggles the mind.
Hi I'm trying to setup my own environment in Power Platform.
A do have a community Environment licence, but i cannot complete all the Microsoft Learning workshops as this environment is limited in functionality.
I tried to create a practice environment at work. However, I do not have the "Developer" option when i try to create my own environment. I do have the "Sandbox" option as one of my types.
But these environments are by default to anyone, unless you explicit limit them to an AD group. I do not belong to an AD group exclusively. Nor can i create one just for myself.
Is there a way to create an Environment that is Private. Where only i can access it?
Erick
As you mentioned the Community Plan have some limitations... And in my understanding when you use a Community Plan you get your own environment where you are the only one with access.
I share with you this documentation link where explain more deeply the details of this Power Apps Plan.
https://learn.microsoft.com/en-us/powerapps/maker/dev-community-plan
Based on the screenshot taken from this link I understand that you are already using a Developer environment.
we are using Microsoft Sync Framework 2.1 in various customer projects for file and database sync. Extended Support will end in 2021.
So my questions are:
What is Microsofts strategy for the sync framework? Is it going to be open source, so we can change if needed ourselves? Is there a successor product that we should / can migrate to?
Is MSSF supported on Windows 10 and Server 2016?
Not sure if my answer really helps, but lets see: Microsoft announced the official release of the "Azure SQL Data Sync" on June 18 2018. It is not truly a successor of the original framework, but it is basically all you get. Other "non cloud" frameworks have also started to fade away, since Microsoft treats server/desktop/on-premise only as an extension to the cloud. As the name indicates, it is targeting Azure and it is not for file sync, either.
I have seen your question also in the "old" Microsoft social network (social.msdn.microsoft.com/Forums/en-US/home). In there they point to this framework in questions related to the original "Sync Framework" since something like 2012 (this was the oldest question I could associate with both frameworks).
I have done quite a bit of looking on the Redmine website, and executed a number of Google searches, but I have not been able to find an answer to the difference between Redmine 2.x and Redmine 3.x
I imagine that, much like Redmine 1 vs Redmine 2, it has to do with the version of Rails that the platform is built on, but I would be interested to know a little more in-depth about the differences and compatibility.
I imagine, also, that plugins are not compatible between the two versions, so this leaves one to wonder, what are the benefits of using one over the other?
Edit: I do see the Rails version difference listed on the Installation page. What is the difference beyond that?
We using Redmine at work, with version 2.3.3
And now we wanted to upgrade to new versions (security updates).
We asked the same question.
And what I founded:
from their news page
This new version brings several improvements to the search engine (it's now much faster and includes new search options) and many new features: default issue status per tracker, multiple emails per user, ability to edit attachment descriptions and more
from their Changelog
...
Feature #13849: Grouped filters in the filter drop-down
Feature #13051: Support any macro in (pdf) export for wiki's and issues
Feature #12097: Multi Thread Support
Feature #8818: Repository user-mapping with multiple email addresses
Feature #11702: Add user/group to multiple projects at once
Feature #4244: Multiple email addresses for each user
Feature #1326: Add / edit an attachment description after upload
...
and more
I am working on a copy of a SharePoint 2007 site for a client.
I would like to be able to automate as much of the update process as I can with minimal disruption to the client's system when the updates are ready for production.
To that effect, I was wondering if anyone knows how to automate creating a SharePoint workflow (created using SPD 2007) in another SharePoint server/site.
Perhaps I haven't searched enough yet, but I have not discovered if there is a way to do this with web services, which I believe would be my preference.
I do not believe I have the ability to use STSadm on this, as the hosting for the SharePoint site is separate.
I think I can export the workflows in a personal web package and I'll admit, I haven't experimented with this yet on workflows, but my current experience with other exports, such as lists, is that guids seem to get messed up between sites. Even if this is not an issue, I'm not sure if there is a way of automating the import process (without STSadm).
I'm hoping not to have to work through a long list of manual procedures (that could accidentally get missed) when implementing these changes on the target production site.
My preference is to be able to create some sort of update batch or application that will make the changes quickly and that I can test before implementing on the production system.
This entails quite a few things, but for now, I'd like to focus on getting workflows into the target system.
Any suggestions on where to get started would be welcome.
SharePoint Designer workflows are not portable between sites. (Reference) 1
For your situation, I would recommend taking the Visual Studio workflow route. Take a look at this tutorial: How to Create Custom SharePoint Workflows in Visual Studio 2008. The key for you is how you will associate it to lists.
The other option is to create a custom Workflow Activity (2007 has less options that 2010). You will still have to create the workflow using SharePoint Designer and add your custom activity to it in each site.
1. Yes, there is the "hack way" of trying to do it by copying the XML and changing the GUIDs... but it is error prone and difficult.
SharePoint 2010 gives more flexibility for workflows and thus the first #Kit Menke statement isn't true for readers using SP2010 (i see that this is tagged as sharepoint2007, but i'm making it clear for readers using SP2010)
However, if you publish a workflow template to a SharePoint site
collection, you can download that template as a WSP file and then
deploy it to other site collections.
Read more about Workflow deployment process (SharePoint Foundation 2010)