I'm working on SharePoint workflow (SharePoint 2010) in SharePoint designer 2010. I was published it many times without problems. But after many publishes (I thing 30) SharePoint stop to changing workflow (I published it without any error and I can find new workflow release in SharePoint web interface).
I published new version (with new commands) but workflow still use old one. But when I modified one of commands which was in workflow previously the modification will appear in next run. I need to add to workflow new commands. My only option is to rewrite whole workflow to new one. But this is much complicated workflow and rewriting takes me long time. Is this behavior normal? Is it some bug? is there any patch or workaround?
This happens most of the time due to the caching mechanism in SharePoint/SharePoint Designer. What you need to do is the following:
Close your SharePoint Designer
Navigate to the following directory: %USERPROFILE%\AppData\Local\Microsoft\WebsiteCache
Delete everything in this directory
Navigate to the following directory:
%APPDATA%\Microsoft\Web Server Extensions\Cache
Delete everything in this directory
Open SharePoint Designer and try to publish your workflow again.
Everything should now work.
For SharePoint Designer 2013 you need to do the following steps:
Go to File > Options > General > Application Options
In the General tab, under the General header, check if the "Cache site data across SharePoint Designer sessions” is ticked. If it is, unchecked it.
Open your SharePoint Designer again and try to publish your workflows.
There is an easy workaround: You need to enable major versioning for the Workflows list. By default, that list is not visible but you still can get to the admin page:
Open SP Designer
Goto All Files
Right-Click Workflows list -> Properties
On the ribbon click Administration Web Page
On the admin page go to Versioning Settings
Enable major versioning
Save your workflow
Related
I had several workflows created in SharePoint Designer 2013 for SharePoint 2013, and I needed to disable some of them before "Creating New Items" in bulk by using a Quick-Edit view, so they would not send e-mails/change values/or create new items, as they were supposed to do if the setting: "Creating a new item will start this workflow.", would have been enabled in the List Settings/Change a Workflow page.
I uploaded the new records with the quick edit method, and then I whent to look for a change that one of the Workflows that I left enabled... ...long story short: Workflows that were disabled, were running... All of them!!
Does someone know why if I disable workflows through the SharePoint UI,so they DO NOT get executed automatically when adding or updating items, they still get executed when adding new items or editing values. Or why the same setting does not seems to be changed if I open the workflow configuration in SharePoint Designer 2013? Do I need to make a change in SharePoint and through SharePoint Designer so the change is honored?
To clarify: If I uncheck the box that says "Creating an item will start this workflow." through the SharePoint UI. Then, save the changes to the list, then; however, if I open SharePoint Designer I see that the box "Start workflow automatically when an item is created" IS ENABLED!!!
Does it is needed to make a change in SharePoint and through SharePoint Designer so the change is honored?
A document in workflow task list is being downloaded when I click on it. it what I expected.
But, when I change the downloaded document. It sync back and changes the document on sharepoint online list.
How can I stop that sync on sharepoint online?
It might be sync to SharePoint work space is enabled. To disable follow the below instructions.
Select the document library. Click Library Settings. Click Advanced Settings under the General Settings category. Under Offline Client Availability category, select No to prevent users from download the documents.
Using SharePoint 2007, how could I allow the adding of CEWP's to the selection menu of an "Add a Web Part" dialog while in Edit Page mode? As of the moment, I can only add Announcements, Calendar, Links, Shared Documents, Tasks but I do not have the ability to add a CEWP. I have full access to the site.
At Site Settings > Site Features > Site Collection Features, you will want to have the Office SharePoint Server Publishing Infrastructure set to active.
Then, on the site, go to Site Settings > Site Features, and activate the Office SharePoint Server Publishing feature. You should then be able to add the content editor web part to the site.
Quite often I see SharePoint 2010 websites without the Content Editor webpart (MSContentEditor.dwp)
To enable this web part you need to activate the BasicWebParts feature on that site. I did not find an option to do this by the web site admin; you can enable the feature however by using SharePoint powershell.
Execute the following statement in the SharePoint Powershell and the Content editor web part will be added to your site
Enable-SPFeature 00bfea71-1c5e-4a24-b310-ba51c3eb7a57 -Url [SharepointSiteUrl]
To get the SharePoint site url just run
Get-SPSite
Gertjanvanmontfooort blog
I ran into a similar issue in SharePoint 2010, but I couldn't see other webparts due to my user permissions on the Site Collection. After getting "Restricted Read" rights on the Site Collection I could see all of the different WebParts.
Here is what helped me fo Sharepoint 2013 Online (Office365):
http://answers.microsoft.com/en-us/msoffice/forum/msoffice_o365admin-mso_manage/problems-opening-a-site-from-sharepoint-designer/d1e71427-be3f-4ea7-be3b-8ba6b64af76c?page=2&auth=1
Basically, I had to set flag DenyAddAndCustomizePages to 0 using sharepoint power shell.
Moreover, from time to time I had to reset the flag to 0 as the online sharepoint seems to reset it to deafult 1.
After trying all the above, and other proposed solutions, my eventual success was through PowerShell script. Admittedly I did check that Custom Scripts was permitted and I did have to Activate the two "SharePoint Server Publishing" features described above, but as I am using a sub-site I presmume something else must have been messed up. In the end the following script allowed me to see the Content Editor option when adding a Web Part:
SET-SPOSite -DenyAddandCustomizePages 0
The full article can be found here:
https://answers.microsoft.com/en-us/msoffice/forum/msoffice_o365admin-mso_manage/problems-opening-a-site-from-sharepoint-designer/d1e71427-be3f-4ea7-be3b-8ba6b64af76c?page=2&auth=1
I'm using Visual Studio 2010 to develop a SharePoint Server 2010 solution. Part of this includes custom Page Layouts, but when editing them, intellisense is completely broken, since Visual Studio doesn't appear to know how to handle them. Here's what I've done:
Created a new blank solution
Right-clicked on the solution and created a new "Empty SharePoint Project"
Right-clicked on the project and created a new "Module"
Renamed sample.txt to MyPageLayout.aspx or created a new ASPX Web Form
At this point, intellisense for the new Page Layout is broken. It gets even worse with tools like ReSharper installed. Also, things like "Format Document" will break the Page Layout (by for example changing asp:Content to asp:content)
What I've tried to get intellisense working:
Added a Web.config from a standard Web Application Project to the root of the SharePoint Project - made no difference.
Added the ProjectGuid for a Web Application Project to the SharePoint project file - broke the project.
Is there any way to get intellisense, and the rest of the support Visual Studio can offer for Web Forms, available when developing SharePoint 2010 Page Layouts?
I have followed your post to some extent.
Using VS2010 (On an x64 machine)
Create a blank SharePoint solution. (this properly combines your #1 & #2)
Add a module (in SharePoint a module is like a folder or resource container)
added a new class to the module (intellisense present)
Added a new webpart to the module (intellisense present)
added a user control to the project designer works and (intellisense present)
I believe that you should consider creating true server or visual web parts. This will have a harder learning curve but will pay with dividends in the future. You will be able to package and deploy your solution again or to another server/farm. Aspx pages can be added and manipulated by the dreaded SharePoint designer. In 2010 the theory is that those designer mods can be packaged and deployed.
I work in this environment every day and the best advice I can give is to embrace the SP object model and do 'it' the sharepoint way. Don't try to force SP to be something its not. :)
This is probably not the solution you are looking for but it's the best thing I found for SharePoint development.
In your solution, create 2 projects :
1 SharePoint Project (empty or not)
1 ASP.NET web application project
Develop all your UI (aspx pages, ascx controls, etc.) in your ASP.NET project and create post-build steps that will copy the pages and controls to the appropriate folders in your SharePoint solution.
That way, you will benefit from all the features of web development in visual studio and it will be very easy to deploy as well. It is a bit of a time investment at first, but it is well worth it if you have any considerable amount of logic to implement in your aspx pages.
This blog post documents what you need to do.
you can add an intellsense to pagelayouts by closing the page and simply reopen it from
file->openfile->your file page layout path
Or you can directly "Right Click" on the file you want to open from the Solution explorer and then select "Open" : you'll get the Intellisense !
I would like to use Sharepoint Designer 2007 as an html editor. I have a web site with a lot of files in a folder on my hard drive. I do not want Sharepoint Designer to make a web site out of this. I just want to use Sharepoint Designer to edit the html files, locally.
If I ever make a mistake and click on a tool for Sites, such as summary or report, Sharepoint Designer will decide that my folder is now a web site. From that point on, Sharepoint Designer is painfully slow whenever I open a file contained in the folder that Sharepoint decided is my web site, instead of being instantaneous like it was before.
I can resolve this situation by renaming the folder containing my web site -- everything gets fast again. I can also fix it by uninstalling and reinstalling Sharepoint Designer. Neither of these is a good solution. Is there a place in Sharepoint Designer, or in application data or the registry that I can kill off the Sharepoint Designer web site that's associated with a folder on my hard drive?
I'm not certain this will fix your issues (as I can't easily recreate the situation you describe). But I do know where SharePoint Designer tucks away metadata about the websites you open and edit.
The next time SPD converts your folder to a web, shut down SPD and delete the contents of the following folders:
WebsiteCache:
XP: C:\Documents and Settings\<username>\Local Settings\Application Data\Microsoft\WebsiteCache
Vista/7: C:\Users\<username>\AppData\Local\Microsoft\WebsiteCache
There is one file in WebsiteCache you may wish to keep, which is Websites.xml. This contains the "shortcuts" you see when you go to File > Open Site...
Web Server Extensions:
XP: C:\Documents and Settings\<username>\Application Data\Microsoft\Web Server Extensions\Cache
Vista/7: C:\Users\<username>\AppData\Roaming\Microsoft\Web Server Extensions\Cache
Whenever SPD gets wonky about reporting which files are checked out/in, really slow to open, or just generally weird, we clean out these folders and things return to "normal".
Hope this helps!