Tag Info

New answers tagged

1

If you have the privileges to do so, make a change in the system registry. [HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\InfoPath\Designer\RestrictedFeatures] "CodeAllowed"=dword:00000001 Restart InfoPath and the Programming option should be available from the Tools menu.


0

I have no experience with Visual studio Workflows but this is probably a general answer. Add option to start manually Add option to start workflow when item is created. In this workflow, you create a variable with the day of today and add 30 days. Then you add an IF condition if the workflow status/completed = untouched/0% and the date +30 == today (the ...


0

You need to copy the dll files from the sharepoint server in the directory C:\Program Files\Common Files\Microsoft Shared\Web server extensions\12\ISAPI to a directory on the local computer, C: \ Windows \ assembly \ GAC.


2

The list instance was created on the site on which you activated the feature. Your list should be in a web-scoped feature. Site-scoped features are for site scoped things like master pages, content types and web parts. They will not cause web-scoped things like lists to become automatically provisioned on subwebs. This means every subsite you want the ...


0

If the Scope is "Site" it creates only at root site level, change it to "Web" and deploy it. Please deactivate, uninstall and retract completely before you deploy your changes.


0

Debugging on Production environment is not recommended. You should use Logging and capture the event/details. If you still want to go ahead then copy solution to one of the web front end server. Then do a deployment using Visual Studio. Since its a farm setup activating feature will fail. So you need to login to central admin and then deploy the solution ...


2

In SharePoint you can configure the outgoing email settings at two locations in the Central Admin. First, there is a global setting at Central Admin -> System Settings -> Configure outgoing e-mail settings (that is what was asked in the original question). Second, you can configure an alternative setting for each of the web applications at Central ...


3

Package a WSP Right click your project in the right column. Then click "Publish". A dialog will open, where you will get to choose where to place the resulting .wsp file. After clicking "Publish" your project will be build and then packaged in the selected location. Make sure to have the Solution configuration set to Release when building for production. ...


3

Well, yes it will. If you have compiled it and packaged it (in a .wsp or .app depending on the technology you use to develop) it will not have any relations to a specific Visual Studio instance


0

Refer below code example: $("textarea[Title='System Description']").closest("span").find("iframe[Title='Rich Text Editor']").blur(function(){ alert($(this).contents().find("body").html()); }); In which the System Description is the rich text editor. For more details here is the great sample explained by Marc: Finding the Contents of a SharePoint Rich ...


1

The method that works best if you have a powerful enough pc (quad core with 16 gig of ram) is to use hyper-v to set up a VM running SharePoint and Visual Studio. You can follow these TechNet instructions - SharePoint 2010 Setup a Development Environment. Failing that and without going down the path of sandbox solutions you have very little choice other than ...


0

Not necessarily. There are some built-in fields (like "Last_x0020_Modified", "Created_x0020_Date") that are lookup fields, but without any lookup list in the background. These are handled by SharePoint internally, and not very well documented.


2

In Sharepoint 2013 one thing called App Step and that it is a mechanism provided to developers of SharePoint 2013-platform workflows (Designer workflows or Visual Studio workflows) to elevate permission of the workflow. you have to do following steps. Allow workflow to use app permissions. Grant full control permission to workflow. Develop the workflow to ...


2

Sharepoint workflows have always run under the context of the user who initiated the workflow process. There were ways to run as the system account in 2007 but that was removed. In 2010 there are impersonation steps that allow actins to run under the context of the person who publishes the workflow. I believe the impersonation steps exist in 2013 as well.



Top 50 recent answers are included