SPD 2013 vs. SPD 2010 issues?

I had been using SPD 2010 for quite some time and one of my sites migrated to SP 2013 so I now have to access using SPD 2013.  The problems I am having are:
1. I use to have a button at the bottom that would toggle between codeview and displayview, where is that now?
2. when I click to edit a default.aspx file I get the error:
This page does not contain any regions that you have permissions to edit
HELP.....
Matt Pinkston

Hi Pinkston,
Whether you could edit other pages with SharePoint Designer 2013.
For your issue, please firstly make sure you have proper permissions on the site. Also you can open the site with SharePoint Designer 2013 using a site collection administrator, compare the result.
Secondly, when customizing a page, there are two modes:Normal and Advanced. Please click "Advanced Mode" under Home tab, then edit the page.
Best Regards,
Wendy
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Wendy Li
TechNet Community Support

Similar Messages

  • VS 2013 Community - Outlook 2010 issue

    I recently installed VS 2013 Professional Community on a Windows 7 Home Premium machine.  Now every time I start Outlook 2010 I get a "Windows Installer - Preparing to install" dialog, followed by a few "Microsoft Visual StudioProfessional 2013"
    dialogs that says "Please wait while Windows configures Microsoft Visual StudioProfessional 2013. . .".  I have the same installation on my laptop & it doesn't happen there.
    Anyone have any idea why, or how to resolve?
      

    Hello Scott,
    Do you have any add-ins registered for Outlook? If so, try to disable them. Does it help?

  • SharePoint 2013 Workflow (SPD 2013) fails for Active Directory Group members

    Hi
    I have a SharePoint 2013 site called "Team Meetings". There are a number of lists and an InfoPath form library.
    The site's SharePoint Group "Team Meeting Members" has two Active Directory groups (All Club Managers and All Club Police) as members. Those two AD groups contain all the people that I want to have  access to the library and list, except for
    a few additional folk who I have made individual members. 
    My PROBLEM:
    I  have created a SharePoint 2013 Workflow using SPD 2013 associated with the  Form Library. Workflow is set to start on new or modified item. The first action is to write to history list, then determine the status (Submitted or Pending) of
    the form and go to different Stages depending on that status.
    The workflow works perfectly for any user who has been added directly to the SharePoint group (Team Meetings Members) BUT FAILS at the very first action for anyone who is a member of one of the AD groups. I know the Workflow is fine because I've tested it
    with numerous people who are direct members of the SharePoint Group, but whenever a person who is a member of the AD group tries it the Workflow just fails.
    Here's a print of the info from the Workflow Status page (I don't have access to server logs):
    RequestorId: 4494760f-92ff-2e8c-90d2-cc7df0e6baa4. Details: System.ApplicationException: HTTP 401 {"Transfer-Encoding":["chunked"],"X-SharePointHealthScore":["0"],"SPRequestGuid":["4494760f-92ff-2e8c-90d2-cc7df0e6baa4"],"request-id":["4494760f-92ff-2e8c-90d2-cc7df0e6baa4"],"X-FRAME-OPTIONS":["SAMEORIGIN"],"MicrosoftSharePointTeamServices":["15.0.0.4420"],"X-Content-Type-Options":["nosniff"],"X-MS-InvokeApp":["1;
    RequireReadOnly"],"Cache-Control":["max-age=0, private"],"Date":["Mon, 10 Mar 2014 01:31:42 GMT"],"Server":["Microsoft-IIS\/8.0"],"WWW-Authenticate":["NTLM"],"X-AspNet-Version":["4.0.30319"],"X-Powered-By":["ASP.NET"]}
    The HTTP response content could not be read. 'Error while copying content to a stream.'. at Microsoft.Activities.Hosting.Runtime.Subroutine.SubroutineChild.Execute(CodeActivityContext context) at System.Activities.CodeActivity.InternalExecute(ActivityInstance
    instance, ActivityExecutor executor, BookmarkManager bookmarkManager) at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor 
    Members of the SharePoint Group "Team Meetings Members" have Contribute Access to both the form library and another list that the workflow writes to as well as the Workflow History list (which in SP 2013 uses the credentials of the
    user who started the workflow, unlike 2010 which used System Account).
    All members of the Team Meetings Members group, whether they are individual members or part of one of the AD groups, have no problems opening and saving forms etc. It's just the Workflow that doesn't like them...
    I am stumped. I've spent many hours searching for a reason for this. There are about 200 people in the two AD groups so I really don't want to have to add them all individually - especially when these groups are managed in AD for a whole bunch of other reasons
    and using the AD groups means I'll basically never have to worry about modifying the SharePoint access permissions.
    Does anyone have any ideas why this is happening and what I can try to fix it?
    Mark

    Hi Lars,
    I'm afraid not so far but we are trying a few things today so I will post back with results.
    First thing we are doing is making the AD Group universal because one of our (external provider) gurus remembers seeing something about that. He also sent me a link to a post where they were talking about earlier
    versions but having similar issues and their solution was to make sure the app pool account has sufficient permissions in AD::
    http://social.msdn.microsoft.com/Forums/sharepoint/en-US/27a547da-5cc0-49d7-8056-6eb40b4c3242/failed-to-start-workflow-access-is-denied-exception-from-hresult-0x80070005-eaccessdenied
    This part of that thread looks interesting but we haven't checked it yet as were trying the universal setting first:
    "If the users participating in the workflows have been added to the SharePoint site via Active Directory groups, SharePoint has to update the user’s security token periodically by connecting to
    the domain controller. By default, the token times out every 24 hours. But if the application pool account did not have the right permissions on the domain controller to update the user’s token, user will keep getting the access denied error. The error was
    intermittent because when the user browsed to any page other than the workflow form, the token was getting updated successfully.
    You can try to fix it through granting the application pool account the appropriate permission by adding the account to the group “Windows Authorization Access Group” in Active Directory."
    I'll update when we try these ideas. If you have any luck please do the same.
    Mark
    (sorry about formatting - using my phone....)
    Mark

  • SPD 2013 Workflow not working

    Hello,
    I'm running into a very interesting issue, we have a 2013 custom list that has some 2010 and 2013 workflows associated with it. Just until recently the workflows were working fine, but now only 2010 workflows are working. 
    I updated one of the 2013, tried to publish it  but then I canceled the process of publishing it because I had to make a new update.... not sure if this flipped the switch on these but now even if I create new ones in SPD they will not run. Also if
    I try to run in manually I get a message - "Something went wrong. To try again, reload the page and then start the workflow"(the option for start manually is enabled in SPD 2013). Any help on this will be greatly appreciated! 

    Hi Ghabib05,
    According to your description, my understanding is that you got an error when you ran a SharePoint 2013 workflow.
    Afer you made some change in your workflow, whether you re-published the workflow. if not, please publish it, then test again, compare the result.
    Please create a new SharePoint 2013 workflow on the list, then test, compare the result.
    If this issue only occurred on the specifical workflow, I suggest you create a new workflow instead of the problematic one.
    If this issue occurred on all SharePoint 2013 workflow, you can try to re-register workflow service.
    Best Regards,
    Wendy
    Wendy Li
    TechNet Community Support

  • Start a Task Process Action in SPD 2013 does not expand SharePoint Groups

    I created a site workflow in SPD 2013, and added a "start a task process".  I specified that the participants would be a group, the tasks would be created in parallel and "Assign a task to each member with groups" is checked. 
    I did check after the fact that "ExpandGroup" is "Yes" in the properties.
    However, when executed, the group gets assigned a task, not individual users within the group.
    I have seen other postings where others have the same issue, but no resolutions besides MS is investigating.  Is this some issue with my setup?  I have tried this in multiple environments with the same results.

    Hi  wangsy101,
    According  to your description, you create a workflow with “Start a task process” in SharePoint 2013 Designer, and the participants was a group, and you had make sure that the “ExpandGroup” was “Yes”. However, when executed, the workflow didn’t assign
    the task to individual users within the group.
    I reproduced the process, and in my testing , everything worked well.
    When you start the workflow and view the workflow, you will see the Assigned to field is the group. And when you open the related tasks, you will note that there are some new tasks related to individual users within the group. It  means that the “ExpandGroup”
    works correctly.
    If the issue still exists, please create an approval workflow  with SharePoint 2010 Designer platform, and set the same configuration to test.
    I hope this helps.
    Thanks,
    Wendy
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • SPD 2013 Workflow - Create list item with people picker in other site collection

    Hi all,
    I read a lot of blogs and forum posts the last couple of days, but I seem to be stuck as to why my workflow is not working as expected - thus, I thought I would ask the experts :-)
    Setup:
    2 lists in 2 different site collections
    http://svr-url/servicedesk/tickets
    http://svr-url/projects/requests
    SharePoint 2013 on Prem
    I try to create a SPD 2013 workflow that creates a new item in list "requests" once a certain trigger is set in list "tickets". One of the fields I need to copy is the requestor = People picker field.
    I did a web service call with a REST call to create a list item. All works well as long as I just stick to Title and other text fields, but filling in the "Requestor" fails with "Bad request".
    I learned I need to use the "RequestorID" field and in a blog I read I need to put in the user id as Int32. So I set the parameters in the dictionary to integer. Still I get "bad request".
    Another issue: as I have lists from 2 site collections, the user id differs for the same user.
    /servicedesk: ID = 9
    /projects: ID = 22
    Additionally, the possibility exists that the user I try to set is not already existent in the /projects user information list.
    How can I deal with that?

    check this
    http://community.office365.com/en-us/f/154/t/127887.aspx

  • SPD 2013 WorkFlow starts in visual mode and crashes when publishing or switching views

    When editing a Workflow in SPD 2013, the WF forces the WF to open in visual mode and I am unable to publish or change  the view without crashing SPD.  When any action is taken on this
    workflow a progress bar flashes and "Exporting Workflow" is displayed --  this process either crashes SPD or locks the computer. 
    I have completed the following
    without success:
    uninstalled & reinstalled SPD and Visio (32 bit),
    cleared caches, 
    uninstalled and reinstalled SPD and Visio to 64 bit,
    installed all updates
    Any guidance is much appreciated.

    Hi,
    Could you test the issue on another machine with both Visio and Designer installed?
    Does the issue occur to all workflows?
    I find similar issue for your reference:
    https://premierpointsolutionstraining.wordpress.com/2014/01/24/sharepoint-designer-crashes-workflow-design-view/
    http://answers.microsoft.com/en-us/office/forum/office_2013_release-visio/visio-2013-sharepoint-designer-2013-crash/424c5720-2ae0-404c-9a53-2a06cddd3365?auth=1
    Please test if updates matters in your situation.
    Regards,
    Rebecca Tu
    TechNet Community Support

  • SPD 2013 Display List View Tools in Ribbon

    When editing a (wiki) page in SPD 2013, and having inserted a Data View (List View Web Part), I find that I quite often am unable to see the "List View Tools" in the Ribbon.  I want to add or change Parameters or Filters, and cannot do so. 
    I go to the correct area of the code, but cannot make the List View Tools appear.
    What can I do?

    Hi Mike,
    Not sure if you have discovered this, but the List View Tools tab is briefly available in SPD 2013 after you insert the WebPart.  Once you save, it is no longer available.
    A bit Ironsides - you have x minutes to use this tab before it self-destructs!
    Regards,

  • Missing Utility Actions in SPD 2013

    Hi,
    I just installed SharepPoint Designer 2013 and found out some of the Utility actions (Find Substring in String, Replace Substring in String, Trim String) missing from the menu.  I got the installer and SP1 update on the download site.  Appreciate
    any help.  Thank you
    Rose

    Hi
    Rose,
    I could not reproduce this issue, my SharePoint Designer 2013 is working well.
    When you create workflow in SharePoint Designer 2013, you can choose 2013 platform and 2010 platform. The 
    2013 platform include the Utility actions (Find Substring in String, Replace Substring in String, Trim String), but the 2010 platform doesn’t include these Utility actions (Find Substring in String, Replace Substring in String, Trim String).So check
    which platform you have used.
    And if you didn’t configure 2013 platform for SharePoint 2013 Designer, you need
    to configure 2013 platform for the SharePoint Designer 2013, then check if it works.
    Here is
    a link about how to configure workflow for SharePoint Server 2013, you can use as a reference:
    http://technet.microsoft.com/en-us/library/jj658588(v=office.15).aspx
    If the issue still exists, please feel free to reply me.
    Best Regards,
    Lisa Chen

  • Debugging XSLT of Business Data List web part in SPD 2013

    I am working on a Business Data List web part in SPD 2013. I want to customize that complex XSLT that got generated by the web part. It will be really helpful, if I can debug that XSLT. But I am not sure, how to debug XSLT from SPD? If at all, I need to
    debug through Visual Studio also, I need the XML also, which I don't have. Can anyone please help?

    Hi Ven,
    XSLT debugging , I have never heard abt it. Its like UI design and you modify it and test it in Browser. Thats the only way.
    one such sample is http://msdn.microsoft.com/en-us/library/cc300164(v=office.12).aspx
    Please remember to click 'Mark as Answer' on the answer if it helps you

  • SPD 2013 - Send an email when a particular list column changes

    Hi
    Using SPD 2013 with SharePoint Online.
    I have a list with a date column, I want my list workflow to notify me when the date column changes to a value other than its created value, ie any change.  How can I achieve this in my workflow please?
    Thanks for your assistance
    Matt

    create an auxiliar, hidden field to save the old value of your column (OldDate).
    create a workflow on item created, and set OldDate = Date.
    then create a workflow on item edited, if (Date !=(not equal) to OldDate do what you want, and set again the OldDate = Date.
    This workflow will execute your tasks only when you update the Date column

  • Sharepoint Foundation 2013 and Outlook 2010 Reminders

    Hello, I have recently been informed by one of my users that they are experiencing a peculiar issue in regards to their SharePoint calendar. A brief history is that we are currently using SharePoint
    Foundation 2013 with Outlook 2010, all of our users have calendars for their departments in SharePoint, and those calendars have been added to Outlook for their convenience. This particular user has a SharePoint alert set up on their calendar for all changes,
    and receives an alert immediately. After some troubleshooting, this is how my user is getting the issue they described:
    User1 will create an appointment from Outlook on the SharePoint calendar that User2 has their alert set up for. User2 will receive the appropriate alert email that there has been a new event
    added to the calendar. User1 then receives an Outlook reminder that their event is coming up. If User1 clicks "dismiss" on that reminder, User2 will have another alert email generated hours later which informs them that the calendar event for User1
    has been modified. If you view the event from SharePoint it will show a new modified time with User1's name, even though there have been no changes made. The other interesting part about the modified time is that it will not reflect when User1 clicked “dismiss”
    on the reminder, instead it will reflect the time that the SharePoint alert email was generated.
    This is not a fluke issue; I've been able to recreate the scenario 100% of the time if I follow this pattern. I can also simulate it on any calendar I create or that is already existing in our
    environment.
    I have been researching and trying to find an answer to this problem for several days now, but the only thing I have found is a post from someone else experiencing the same issue with no solution.
    So any feedback would be greatly appreciated. If there is more information that is needed to better assist me, please let me know.
    Thank you for your time.

    Hello, if I remember correctly the issue was that I created the form with InfoPath 2013 and was trying to test using InfoPath 2010. This does not work.
    Did you create the form using InfoPath 2013?

  • Is Lync 2013 and Office 2010 Home and business compatible?

    hi,
    Is Lync 2013 and Office 2010 Home and business compatible?
    tnx

    Lync 2013 and office 2010 is compatible with limited features
    The following features are available only with Office 2010 or Office 2013:
    Contact card with expanded options, such as video call and desktop sharing
    Quick search from the Find a Contact field in Outlook
    Reply with an IM or call from the Outlook Home ribbon in the Mail, Calendar, Contacts, and Tasks folders
    Lync Contacts list in Outlook To-Do Bar
    Office Backstage (File tab) presence status, program sharing, and file transfer
    Presence menu in Microsoft Office SharePoint Workspace 2010 (formerly Microsoft Office Groove 2007)
    Presence menu extensibility
    Also you can refer below link
    http://technet.microsoft.com/en-us/library/gg412817.aspx
    For your issue, verify from lync version {for example , if your office 64 bit, Lync must be 64 bit also}
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
    Mai Ali | My blog: Technical | Twitter:
    Mai Ali

  • First Exchange 2013 server in 2010 Deployment - 2010 edge is routing SOME inbound mail to new server where it fails.

    I have a Barracuda filter receiving all inbound internet mail which delivers to the edge server (both in DMZ).  I have one 2010 edge server and one 2010 ht,cas,mailbox server.   I have added a 2013 server and started working
    on configuring virtual directories.  This is a far as I have gotten. Goal is once new box is working to move all mailboxes to 2013 server and remove 2010 mail box server and keep Barracuda and 2010 edge server to pass mail to the 2013 box.
    My issue is the edge server is already passing inbound internet mail to the new 2013 server.  I see the mail being accepted by the Barracuda and message tracking on the edge shows it as delivered to the new 2013 server, but mailbox
    users never receive.
    Is my solution to simply create a new send connector from the 2013 server to the 2010 box or could this be something else?
    And why is it delivering to a server with now mailboxes on it yet?
    Thank you for any help
    dean

    Hello Dean,
    I understand that the message tracking log indicates the email delivered to Exchange 2013 server. Please check the message tracking log on both Exchange 2013 server and Exchange 2010 server.
    How about the result? Have you created new 2013 mailbox and tested if it works?
    As for the send connector, actually an intra-org send connector will be involved for internal mail flow within an organization. So there is no need to create another send connector.
    In addition, I’d like to share you an article about Edge Subscriptions:
    Title:
    Understanding Edge Subscriptions
    Link:
    http://technet.microsoft.com/en-us/library/aa997438(v=exchg.141).aspx
    Regards,

  • Outlook clients cannot connect Exchange 2013 cutover from 2010

    Hello,
    My company has been running an Exchange 2013/2010 coexistence. Currently, Exch 2013 (2mbx and 1 CAS) utilizes "mail2.domain.com" for the name space. Exch 2010 (1MBX 1 CAS) uses "mail.domain.com"
    We recently attempted to cutover external and internal DNS to point "mail.domain.com" and "autodiscover.domain.com" to the Exch 2013 server. 
    We changed all virtual directories on 2013 to use "https://mail.domain.com/owa" (ECP, EWS, etc. were changed too) for the internal and external URL. The Exch 2010 virtual directories internal URL are set to "https://internalFQDN.domain.com/owa"
    the external URLs are $null
    Both CAS servers were setup to use Outlook Anywhere since this is how 2013 proxies to 2010. The internal URLs for both were set to "mail.domain.com" IIS authentication Methods (Basic, NTLM). ClientAuthenicsationMethod: NTLM.
    For both servers the autodiscoverserviceinternaluri was set to: https://autodiscover.domain.com/autodiscover/autodiscover.xml
    The 2013 server has two SSL certificates installed. One is a wildcard cert for "*.domain.com" and the other includes our SANs (mail.domain.com, mail2.domain.com, webmail.domain.com, autodiscover.domain.com) it also includes the FQDN for the 2010
    and 2013 CAS servers.
    I'm speaking in the past tense because we had to roll back. The problem was no Outlook user could connect. This goes for mailboxes hosted on the Exchange 2013 and 2010 servers. The error was: "Cannot
    open your default e-mail folder" to "The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete".
    Everything else worked fine during the cutover. OWA 2013 login page proxied 2010 logins properly, Outlook 2011 could connect with EWS fine, Active-Sync worked without issues too.
    It was only the Outlook 2010 and 2013 clients that could not connect.
    We rolled back and everything is working as it was before with the separate namespace. That leads me to think it's something with Outlook Anywhere (RPC/HTTPS)
    but the settings seem correct unless I'm missing something. Any help is appreciated.
    Thanks!

    Hard to say. I've had to change the router to point to the old server as mail wasnt getting in. But OWA did seem ok, although I couldn't send messages... I could only see the inbox and contacts etc.

Maybe you are looking for