Tag Info

New answers tagged

0

I have the same problem, and work around it by starting a 2010 workflow from within my 2013 workflow. The 2010 workflow does the lookups and sets parameters with the looked-up values (usually the ID number from the parent list). These parameters are then available to the 2013 workflow.


0

I had the same challenge and to resolve it this is what I did: I moved out other site collections from the content database containing the bad site collection using the command below Move-SPSite http://servername/sites/sitename -DestinationDatabase ContentDb2 iisreset I deleted the faulty content database using the command below: Remove-SPContentDatabase ...


0

Finally I found it, apparently this does work but thows an error: this.oListItem = oList.getItemById(1); ctx.load(this.oListItem); ctx.executeQueryAsync( Function.createDelegate( this, function () { console.log("scriptAddMenuToListView.js: AppWebUrl successfully retrieved from lstAppData..."); var xAppWebUrl = ...


2

The problem is the URL format that you are providing to the net use command. Take a look at the PowerShell script here http://www.lieben.nu/numb3rs/?page_id=129 which automates mapping a drive letter. You will see the format of the parameter is like this: \\domain.sharepoint.com@SSL\DavWWWRoot\sites\codesite\example\Shared Documents If you would ...


0

This error typically arises when we try to access a field that was not requested. Try below ctx.load(this.oListItem, 'Include(xValue)');


-1

Run code in SPSecurity.RunWithElevatedPrivileges


-1

I have faced a similar issue couple of days back. For couple of reasons the related DLLs will not be un-installed from GAC. I deleted the solution respective DLLs from the GAC forcefully followed by an IIS Reset. It worked for me, Hopefully that's the solution for your scenario.


0

Please try the answer provided here. In my scenario this post helps. http://sharepoint-360.blogspot.in


0

As soon as it is "customized" (formerly known as "unghosted"), the reference to [the master page] for that site is in the database, not the file system. Without a change to web.config, code blocks are not allowed. SharePoint disables the ability to create server-side script by default, you have to turn it on. You do that in the web.config file, in the ...


-1

I had the same problem in Sharepoint 2010. All my reports used shared datasets. I had to remap the datasource for each dataset and this solved my problem. Thanks for your help.


0

So from your Error and other descriptions( as you are using the Publishing Portal.). I think your issue fall under the object cache settings. Please configure the Object cache on your web Application. Configure object cache user accounts in SharePoint Server 2013 As Alternative( or testing), you can create a team site and then test it, I am sure it will ...



Top 50 recent answers are included