Having issues deploying your tenant scoped SharePoint add-in (though I confess I still call them apps)? You've pasted the XML for your add-in on the appinv.aspx page and you get a message back that you have to be a tenant admin? But wait you are logged on as the tenant admin!
Microsoft recently made a change that any apps that require tenant permissions must use the tenant admin site itself for the AppInv.aspx - so navigate to https://mytenant-admin.sharepoint.com/_layouts/15/appinv.aspx and try out the same steps - it'll work just fine!
Makes sense I guess that in order to deploy a tenant scoped add-in I really should be a tenant admin... I haven't tried to verify whether I need to be a global admin or just a SharePoint admin, but I suspect both would work fine.
Monday, September 12, 2016
Tuesday, August 16, 2016
SharePoint Designer, Workflows, local cache
Hi world, been a long time! I'm still SharePointing, been having fun with client side rendering and JSOM. Post on that coming soon, promise!
In the meantime, here's a quick one. Admit it, you still use Designer. It's still a handy tool especially for workflows. I had put together a workflow for one of my customers, it's been working just fine. Occasionally, though, when I went to edit it, I would get an error generating local caches. There's some recommendations on how to clear out the local cache & try again, but that didn't seem to help me. I tried on multiple PCs and VMs and finally got one working, then three months later promptly forgot which combo actually worked...so time for that root cause.
What did help? Run as Administrator. Yep, the issue wasn't in pulling down the content for the caches, but getting that content into the local file system. I'm logged on with a local admin account on my dev VM, but even so that didn't help. So, with your nifty Designer program icon, hit Ctrl + Shift then click, accept the prompt to run as Admin, and edit those workflows away.
See you soon! The big teaser is, re-running a workflow when an item is edited on O365. It can be done.
In the meantime, here's a quick one. Admit it, you still use Designer. It's still a handy tool especially for workflows. I had put together a workflow for one of my customers, it's been working just fine. Occasionally, though, when I went to edit it, I would get an error generating local caches. There's some recommendations on how to clear out the local cache & try again, but that didn't seem to help me. I tried on multiple PCs and VMs and finally got one working, then three months later promptly forgot which combo actually worked...so time for that root cause.
What did help? Run as Administrator. Yep, the issue wasn't in pulling down the content for the caches, but getting that content into the local file system. I'm logged on with a local admin account on my dev VM, but even so that didn't help. So, with your nifty Designer program icon, hit Ctrl + Shift then click, accept the prompt to run as Admin, and edit those workflows away.
See you soon! The big teaser is, re-running a workflow when an item is edited on O365. It can be done.
Subscribe to:
Posts (Atom)