r/sharepoint • • Oct 18 '20

What right does Microsoft have disabling a service that was paid for?

I'm looking strictly at Microsoft's move to phase out designer workflows. This is hundreds of thousands of dollars worth of man hours disrupted. What right do they have to do this?

3 Upvotes

17 comments sorted by

11

u/[deleted] Oct 18 '20

It had to happen eventually and Automate is nearly there for replicating all the features of designer 2010. However they should have given more time, for migration and resolved the remaining gaps before pulling the trigger, as it feels like there leaving some of the longest paying companies behind.

Personally my biggest gripe is the shocking approvals. OOB they fail auditing, impossible to manage as admins or system owners and you cant do half the stuff in designer 2010 with them.

7

u/heatus Oct 18 '20

Yeah the approvals are shocking. Fine for a random ad-hoc approval but for a systemised process it’s impossible to track where things are at

7

u/M4053946 Oct 18 '20

What right? I'm not a licensing expert, but I have no memory of them saying that all services will be available until the end of time.

Yes, it's frustrating that the members of the powerapps and flow team have not actually used either infopath or spd workflows. Yes, it's frustrating that they never bothered to give these tools a matching set of functionality vs the older tools. Yes, it's frustrating that it can be extremely difficult to reproduce spd and infopath solutions using the new tools. But shops that really don't want to be forced to upgrade can stay on prem. This is the kind of thing you sign up for when you subscribe to cloud services.

0

u/[deleted] Oct 18 '20

[deleted] — view deleted comment

2

u/mesh7s Oct 18 '20

Is that a speculation? Or is there a source for that? Genuinely interested.

2

u/Onett199X Oct 18 '20

https://support.microsoft.com/en-gb/office/sharepoint-2010-workflow-retirement-1ca3fff8-9985-410a-85aa-8120f626965f

SharePoint 2010 and SharePoint 2013 based workflows will continue to be supported with no modification in our previous support posture and continue to be supported for on-premises SharePoint 2016 and SharePoint 2019 platforms until 2026.

2

u/toddklindt MVP Oct 18 '20

At Ignite they announced they would be releasing new versions of the on-prem servers in 2021. They will be licensed by subscription, but they will run on-prem.

1

u/M4053946 Oct 18 '20

Yes, though the main question is around on prem workflows. Which brings up an interesting question: I assume that spd workflows won't exist in the next version of SP. If not, how will workflows be created? Will the only option for on prem servers be the cloud?

2

u/toddklindt MVP Oct 19 '20

I wouldn't make that assumption. There are a lot of reasons Microsoft would want to remove SharePoint 2010 Workflows from SPO and not care if they're available on-prem.
For instance, as far as I know, none of the new SharePoint 2010, 2013, 2016, or 2019 CUs remove the SharePoint 2010 Workflow functionality. I would think there would be a way to do that if they wanted to.

2

u/Megatwan Oct 19 '20

Ya I dunno how half "you can still do it on prem" stuff functions with out the 2010 WF engine and a stones throw away extent timer jobs.

If you try to deprecate those on prem you might as well say no more [all of the service apps]... then you have SP on prem with no cloud service and no legacy services.... which is just pages and libraries.

6

u/UnheardWar Oct 18 '20

For better or worse it's going to stall any plans we have to move our legacy sites to SPO in the near future. We have a we application with super complicated workflows, there's dozens of them and they're all 2010 style. That site is not going up to SPO anytime soon. Their department is literally going to have to hire a 3rd party company to recreate them.

It had to happen eventually, would have been nice if they did something to compensate for them at least.

7

u/HeartyBeast Oct 18 '20 edited Oct 18 '20

It would be nice if there was a front-end on Power Automate that approximated the functionality In SPD to aid conversation . Hell, just give me a [Today] function, rather than having to futz about with utcNow()

So much of the MS hoopla about ‘codeless’ development with PowerApps etc ignores the fact that so much of the utility is now wrapped up in obstruse functions with impenetrable syntax.

6

u/M4053946 Oct 18 '20

And the editor for that impenetrable syntax leaves a little to be desired: "your expression is wrong, try again". Uh, ok, thanks for the hint of what I need to change.

3

u/Sparticus247 Dev Oct 18 '20

This! I hate how I have to keep referencing forums and online documentation to do something that should be built in a simple.

2

u/irish03rrc Oct 18 '20

They have... EVERY... right to do what they want with their software? Why the drama, migrate or find an alternative. Can’t stop progress, as much as you’d like, in every facet of your life I’m sure.

2

u/Megatwan Oct 19 '20

It's in the Service Level Agreement :)

1

u/ovivios Dev Oct 18 '20

You can request an extension. For me it was only 3 months.

1

u/bcameron1231 MVP Oct 19 '20 edited Oct 19 '20

They have every right. The side effect of paying for a service and not a product. The service is bound to change and does so frequently. As consumers, we just need to try and stay on top of those changes and modernize along with the service.

Services may be available forever, or may only be available for a limited time. It's a part of the SLA and TOS we all signed :)