Posts

Create Form sets in Plumsail Forms for SharePoint

Image
                                Create Form sets in Plumsail Forms for SharePoint How Form Sets are created ? Open Plumsail Forms designer Default Form Sets can be opened by any user unless they are redirected to custom one. To create a new form set, click on "+" sign next to form set name, give it a name and click save. To change form set name and properties click on pen icon Routing based on Azure AD group In our scenario, we have already created a default form and custom form set. In default form, all fields are read only. Full control form set should open automatically for AD group Click on the Pen icon under Azure AD group tab, write group name and search, select the group that you need. You can select multiple users & groups if needed. Testing of sample users: Jane does not belong to Admin ID group so the entry created by her is not routed to other form but to default form. Elizabeth Holmes belong to Admin ID group so the entry created by her is routed to "Full

Deploying Farm Solutions Containing Web Parts to SharePoint 2013, 2016, or 2019

Image
Go to Visual Studio    Choose New Project    In Office/SharePoint tab, Choose Empty SharePoint 2013/2016 - Empty Project      Add Webpart Item Add WebPart Group   Rename Feature Right Click> Deploy Go to SharePoint Site>Site Contents>Site Pages Click on gear icon, edit site Add a WebPart Go to Site Settings> Site Collection Features Go to Visual Studio and right click on the Project In the SharePoint Server,  Go to SharePoint Central Administration site>System Settings>Farm Management>Manage Farm Solutions    If there are no solutions installed Right click on the solution package and Copy as Path Go to SharePoint 2016/2013 Management Shell   Come back to Solution Management in Central Administration Click on the solution name Click on Deploy Solution. Ignore the error as we have to make changes in GAC to deploy farm solution Activate Site feature from Site Settings>Site Collection Features Thus Farm Solutions Containing Web Parts to SharePoint 2013, 2016, or 201