Related
SharePoint lets you save sites as a site template so that you can configure a site the way you want, save it as a site template and then create more identical sites from the template. You can save old-fashioned 'SharePoint workflows' into site templates so that the new sites automatically have the same workflow provisioned.
Is it possible to save Flow / Power Automate within a SharePoint site template? Or is there an alternative approach to achieve the same goal, e.g. so that when a new SharePoint site is created it has a specific Flow / Power Automate set up automatically?
We have an ongoing system. In that system, we have used a custom form in SharePoint online, when a new item added to the project list using custom form one project site automatically based on a custom site template. That custom site template contains SharePoint designer workflows. Lists Templates, Web Parts, tec.
Nowadays Microsoft has been retired Sharepoint designer workflows. So, we need to migrate Sharepoint designer workflows to Power Automate. Power Automate is working fine for one site but we need to add that Power Automate with SharePoint custom site template. So, when the new site is created flows are created automatically like Sharepoint designer workflows
Can you please help me with the above scenario
Site Designs are an option for SharePoint templates. They can be a bit limited but they do allow for extensibility as they can execute a power automate flow as part of the provisioning process. The core provisioning logic here is rather simple: lists, site columns, theme application, content types, and a bit more. Pages are not part of the provisioning schema but they can always be provisioned as part of the flow process.
The nice thing about this is that the provisioning can be done all within SharePoint for kicking it off and getting the basics in without any custom service. Furthermore, if you need user input you could use SharePoint framework to add some sort of form on the provisioned site to 'finish' the provisioning process via an extension, I believe there is a Github out there that does exactly this.
I have a site developed in core .Net with SQL server Database. Now i want to redesign my site using Sitecore. How the data/content can be migrated from SQL database to Sitecore CMS?
Sitecore has released the Data Exchange Framework. This tool allows you to sync content from third party application. Example:
Read contacts from a CRM and create contacts in xDB
Update a contact in CRM using information from a contact in xDB
3.Create items in Sitecore that represent products in a catalog
So, you can easily use this tool to import your data from sql to sitecore. You only have to develop the different logic that requires to translate the data from the SQL to the template of your new instance.
Here is the link where you can have the 2 released version:
V1.0: https://dev.sitecore.net/en/Downloads/Data_Exchange_Framework/1x/Data_Exchange_Framework_10.aspx
V1.1: https://dev.sitecore.net/en/Downloads/Data_Exchange_Framework/1x/Data_Exchange_Framework_11.aspx
From the links, Sitecore has already specified the released note, required documentation about the API and so on.
I'm a Sitecore beginner, working on Sitecore 8 with ASP.NET.
There is a page where an Ajax call has to be made to get data.
Created a test web service in the project which responds to the ajax call with success. This service will be a wrapper.
I understand, I have to consume one of the 3 options (in the title) inside the test service, to get the Sitecore items and do stuff.
But all 3 appear similar to me & not sure which one to go with, to achieve my task
Also,
1. Is there an advantage of one over the other.
2. ..and when to use which one.
Sitecore Services Client is the framework or namespace that both Item Service and Entity Service sit within. Item Web API is the legacy framework.
Use Item service if you want to do basic stuff with the sitecore Items as this is a prebuilt api. Entity Service allows you to create your own API using the Sitecore.Services.Client framework and give you much more power and control.
https://mikerobbins.co.uk/2015/01/06/entityservice-sitecore-service-client/
Use can also use Sitecore.Services.Client to do the routing and you write the controller. see https://mikerobbins.co.uk/2015/06/25/sitecore-service-client-servicesapicontroller/
I have a requirement to build a service endpoint to provide specific Sitecore 8.0 items (containing a given field value in a given branch of the content tree) to requesting mobile app clients. Encapsulating this logic (and perhaps some other calculations, etc) means the out-of-the-box API is not suitable.
I'd like to mimic an existing SOAP service exposed by another CMS, however I'm not above using a modified version of the RESTful itemWebApi if it confers greater code reusability or upgrade-safety.
Based on my research thusfar, it would appear my options are to build a custom handler, a completely separate asmx service (ala this approach), or to build a custom controller (similar to this custom Web API controller method).
Overriding or replacing the default pipeline processors for the itemWebApi does not seem viable, as I don't want to replace/modify the OOB API if I can avoid it.
Has anyone with the same type of requirement for Sitecore 8 found a better approach?
The approach I chose was to create a separate service "router" developed using the adapter pattern to be consumed by our mobile app clients. The router in turn calls the Sitecore ItemWebApi.
This fit my needs the best as it is completely decoupled from the Sitecore application and the client can be modified if necessary without impacting the endpoint.
It would also be worth looking to EntityService within Sitecore.Services.Client in Sitecore 8. Its a Web API based service but has more flexibility over the standard Sitecore Item Web API because you can define your model and the business logic yourself.
I can see you have mention my other blog post on adding a custom Web API controller. Enitity Service is different, it's a framework by Sitecore to achieve a standard way of creating custom web service for Sitecore.
I have written a blog post on EntityService. It has both a Javascript and standard rest based API to communicate with the service too.
http://mikerobbins.co.uk/2015/01/06/entityservice-sitecore-service-client/
Example Application here: https://github.com/sobek1985/EntityServiceDemo
And a few more posts on advanced features in Entity Service: http://mikerobbins.co.uk/category/sitecore/sitecore-service-client/
I have a requirement of a custom grid in Microsoft Dynamics CRM 2013. From a SharePoint perspective, it would have been a web part. But in CRM 2013, I don't see a similar concept. I need the custom grid to be displayed in a pane for an Entity in CRM? How could that be implemented if possible? Any ideas?
Your question is to broad, but i think what you mean is how to make a custom web page in CRM.
In Dynamics CRM 2013, you cannot add a custom aspx page, as part of a CRM,
you can only put custom Silverlight and HTML/Javascript powered web pages, the latter being the preferred way, of creating these.
However if you need to create a custom web application, you can create it as a separate web application in a separate IIS website, use the CRM web services to access data, and then embed this web application in an iframe on an entity form in CRM.
In order to connect to the crm web service, from custom apps you can use early or late binding.
Early binding sample code
Late binding sample code
Personally i use late binding as connection is easier and it seems to have better performance. The simplest way to obtain a connection to the CRM service for CRUD operations is the following code:
string connString = "Url={DynamicsCRMUrl}; Username=username; Password=password; DeviceID=AnyDeviceId; DevicePassword=AnyDevicePasscode";
CrmConnection crm = CrmConnection.Parse(connString);
IOrganizationService service = (IOrganizationService)new OrganizationService(crm);
For crm online and IFD configured CRM you must add the DeviceID and DevicePassword, for on premise it is not necessary.
Make sure you have the CRM 2013 SDK for the required assemblies.
I am answering the question with a long shot, with assumptions, as i am not sure if this is what you require, but i hope it gives you guidance.
You can add an HTML WebResource in CRM that contains the grid to be displayed.
Depending on what you want to display on the grid, the data could be populated using the Dynamics CRM SDK REST API. (see SDK.REST.js).
Once you have set-up your HTML web resource, you can then include it in your entity form as an iframe component (similar to a SharePoint web part).
This approach means you don't need to host the grid in a separate website, but can include it as part of your CRM solution.