Tag Info

New answers tagged

0

if I understand you correctly, you want to create a view where only specific items from a list are shown? if you can filter the item list according to specific entries this can easily be done in the view settings menu, or you can create an additional column and set that to a value that you can filter for, you don't even have to display that column in the ...


1

In a sandboxed solution cannot deploy files within the SharePoint root directory or any other location on the file system of the web server. That means you cannot deploy branding files to familiar locations that are commonly used in farm solutions, such as the IMAGES directory or the LAYOUTS directory. You must instead provision branding files, such as ...


1

In Sharepoint online you can not deploy files to the _layouts folder as there is no _layouts folder there. For Sandbox solutions, the Style Library is the correct location. If you are going to keep them in the Style Library can try referencing the scripts using the ~sitecollection replacement token (generally Style Library is only provisioned at the root ...


0

Probably the User Code Host service wasn't started in your farm. This service needs to be started for sandboxed solutions to be able to execute (sandboxed solutions are run in this process in isolation, so as soon as your sandboxed suction contains server side code, it needs to be started). What the script you post does is configuring this process to log to ...


0

Official text on MSDN: http://msdn.microsoft.com/library/office/jj163114.aspx Emphasis mine: While developing sandboxed solutions that contain only declarative markup and JavaScript -- which we call no-code sandboxed solutions (NCSS)-- is still viable, we have deprecated the use of custom managed code within the sandboxed solution. We have introduced ...


1

Developing sandboxed solutions that contain only declarative markup and JavaScript -- which we call no-code sandboxed solutions (NCSS) -- is still viable, the use of custom managed code within the sandboxed solution is deprecated. They have introduced the new SharePoint app model as a replacement to those scenarios that required the use of managed code. ...


1

Strangely enough, this fixes the problem for me on SharePoint 2013 instance installed on a Windows Domain Controller: Set-SPLogLevel -Identity "SharePoint Foundation:Sandboxed Code Service" -TraceSeverity "Verbose" Restart-Service -Name "SharePoint User Code Host" Of course, I only use this in a non-production environment.


1

If the solution contains an assembly, only a site collection administrator can deploy it. If the solution does not contain an assembly, a user who has the Full Control permission level at the root of the site collection can deploy it. http://technet.microsoft.com/en-us/library/ee721992(v=office.14).aspx Now Fix to this problem. Add the account into Site ...


0

You can choose Run as different user in Visual Studio and give a site collection admin's credentials when starting Visual Studio. Else you can add the current user as a site collection admin and proceed further.


0

Execute a search with the following syntax: Path:[the_path_of_the_site] Modified=[the_date_in_YYYY-MM-DD_format] KQL Reference: http://msdn.microsoft.com/en-us/library/office/ee558911%28v=office.15%29.aspx


1

The reason for introduction of Sandboxed Solutions was giving ability to work on a partially trusted environment. Without disturbing the Farm Administrators, the Site Collection Admin can handle the deployment. This runs under a set of security policies said CAS Policies. Also with this Sandboxed solutions come under several limitations. Here are some ...


1

One thing that I can think of is workflow association you mentioned. Coded workflows are not allowed in Sandboxed Solutions. Still you can have declarative workflows. Why don't you debug and see? Also check for ULS Logs and Event Viewer events.


0

Sandbox is an isolated environment that do not allow you to call anything outside that environment. A call through a web url away is a call outside the sandbox, requiring System.Net.WebPermissions. This is prohibited by the Code Access Security policies defined for the Sandbox. You have 2 options here. Use JavaScript Client Object Model Build a Sandbox ...



Top 50 recent answers are included