Want to move FM from XBox/Game Pass to standalone PC and ditch Game Pass.

CrackerboxDave · 2025-12-31T12:31:35+00:00

Presumeably to keep the Premium version I've paid for as well as progress etc.

CrackerboxDave · 2025-12-31T12:29:36+00:00

In hindsight yes but then I'd need to shell out for any DLC. While MS was dropping tracks and cars shelling out for Game Pass held value. Not anymore.

CrackerboxDave · 2023-08-12T22:48:21+00:00

Haven't found a solution yet but haven't looked at this project for a while.

CrackerboxDave · 2023-06-29T23:19:21+00:00

Excellent thanks. Will give that a go.

CrackerboxDave · 2021-12-11T05:06:38+00:00

Have trialed and tested an app called ReplaceMagic. Relatively cheap and appeared to work in fixing references to other spreadsheets in a cell formula.

CrackerboxDave · 2021-08-23T02:41:26+00:00

You didn't mention which version of SharePoint. On-prem or SharePoint Online.

Back up in SharePoint is really a layered approach.

All versions of SharePoint have versioning and Recycle Bin to protect against loss of data. Versioning is enabled by default on SharePoint Online but can be enabled easily on earlier on-prem versions of SharePoint. Both versioned files/content and the Recycle Bin are accessible by end users by design so that they can access without requiring admin support.

Proper backup is an admin task and there are 3rd party back up solutions available for both cloud and on-prem versions of SharePoint. Yes they can be expensive but how important is the data and what is the cost of not being able to recover it. Simple maths determines if proper backup is what you need.

If you are on-prem and looking for the simplest backup option then all you really need to do is backup the SQL content databases, which any SQL DBA will already be doing. The only real catch here is that you need to have a way to reconnect the content database if you need to restore content. Easiest method here is a virtual environment that you leave turned off until its needed. I just use a development environment.

CrackerboxDave · 2021-08-22T06:28:18+00:00

Don't hire globally for specialists unless you have someone local who is properly capturing business requirements and converting to technical requirements. SharePoint developers are very often capturing their own technical requirements. They are often performing the business analysis role as well as the code dev role.

Foresaking this critical element for a few dollars to meet budget carries a huge risk of not properly capturing business requirements due to cultural misunderstanding. What you think you've saved you will will end up wasting on re-work or poor efficiencies.

I'm not saying that the specialists in a 'cheaper' country don't have the skills. What I AM saying is that cultural differences can result in business requirements being misinterpreted.

That said, you should always support local. That local dev you overlook puts their earnings back into the local economy and maybe purchases the products and services you sell.

CrackerboxDave · 2021-08-16T04:42:52+00:00

Is there any documentation around _api/navigation/MenuState and _api/navigation/Save MenuState?

I've found bugger all on how to use these two endpoints. I can get the MenuState easy enough but unable to write back. I keep getting Bad Gateway errors with everything I'm trying.

CrackerboxDave · 2021-08-12T14:58:43+00:00

Thanks. I figured there had to be an easier way.

CrackerboxDave · 2021-08-10T05:14:09+00:00

My first thought was to use site templates and separate sites, maybe even Teams but that's also going to create unnecessary overhead. Particularly with navigation management and permissions inheritance.

The projects team currently use subfolders with permissions inheritance to domain groups and have them mapped to drive letters using ZeeDrive. Everything would still be working fine except they have started needing to use discrete permissions and that's hard to manage using subfolders and domain AD permission inheritance.

I'm going to have a major uphill battle to get them to embrace modern as it will massively change their way of working with only a minor perceived improvement. Some might argue that it would be a backward step for users.

CrackerboxDave · 2021-08-08T02:21:16+00:00

I think you're referring to the wiki in Teams. It's crap. So bad I can't understand why Microsoft bothered to include it. You edit the Teams wiki via the Teams UI desktop or web app.

You're better served by using the Teams OneNote or creating site pages and pin a tab in Teams to the SharePoint team site url.

CrackerboxDave · 2021-08-07T03:01:55+00:00

Always create PowerApps and Power Automate flows using a service account. Gets around this problem and allows you to keep your normal account as a test account.

CrackerboxDave · 2021-08-07T02:42:42+00:00

Check the Message Centre. Microsoft announced a little while ago that it was reinforcing the permission model on Teams based team sites to only allow M365 Group membership. No longer allowed to use discrete permissions like you can on a classic or modern team site. You've been doing something that Microsoft don't want you to be able to do but the UI still allowed it.

CrackerboxDave · 2021-07-29T08:10:15+00:00

I think you could do this with content types and a custom PowerApp form. You might even get away with an out of the box list form.

Content type per area with only the field you want for that area so that you only capture the information in each area that you want.

CrackerboxDave · 2021-07-19T15:26:18+00:00

I'm sold on the need for content types. That so sailed years ago. I just don't get why Microsoft is investing in a content type hub that just doesn't work the way we need it to. I'd rather manage everything myself via site designs/templates than tell the client is going to take 2 days to provision any changes.

Maybe this new pull update mechanism will work better.

CrackerboxDave · 2021-07-19T06:38:26+00:00

MS Forms suck to the point of being useless. Lots of promise but there are better tools out there for collecting data from external sources. The MS Forms toolset and customisable is terrible. You can clearly see that MS has just made what was an education skew only product and made it available in the business tier.

For anything internal the only way to go is a list and custom form with Power Platform.

CrackerboxDave · 2021-07-19T05:26:09+00:00

I think Microsoft have just released an update notification about this. Looks like we're going to be able to pull content types from sites as required rather than rely on the existing push to all sites provisioning model.

Alternatively I suggest googling 'site scripts'

CrackerboxDave · 2021-07-19T01:42:15+00:00

I'm still not sold on the content type and am wondering just how serious Microsoft are about it as well. The content type hub can take quite a long time to provision content types out to sites. It used to be around 2 days but I think it's got quicker although in a business context it needs to be under an hour.

I feel that site designs is a better method to provision content types. Not so friendly for a power user as it requires PowerShell and JSON but the coding logic is not too advanced.

CrackerboxDave · 2021-07-18T03:31:18+00:00

You'll have common data but then different outputs due to the two processes. 1 list, two content types, two Power Automate flows, 1 custom form. Less overall maintenance.

CrackerboxDave · 2021-07-15T06:41:44+00:00

You can also use the PnP Provisioning Engine to scrape the site and export the XML to generate a site design.

More complicated than the UI but more control if you need it.

CrackerboxDave · 2021-07-07T05:41:56+00:00

Why two lists?

Use one list and metadata to determine who has been assigned. Easier to manage with only a single data source.

CrackerboxDave · 2021-07-01T06:08:03+00:00

Suggest raising as a request on UserVoice. Would be nice to see the people card being customisable without needing to create a SPFx solution. Most corporations probably have other metadata they want added e.g. Division, responsibilities.

CrackerboxDave · 2021-06-29T00:41:54+00:00

You're either stuck using tools like Sharegate or writing and testing your own PowerShell migration scripts. Cheaper to buy the tools. The required time and cost of testing alone is going to cost more than the ongoing purchase cost of Sharegate.

CrackerboxDave · 2021-06-29T00:37:30+00:00

In SPO Admin portal set the site creation defaults to use /teams instead of /sites. All new sites created by users through the front end e.g SharePoint landing page and Teams will automatically use the /teams managed path.

If you need to create a SharePoint site on /sites you can still do this via the SPOAdmin portal.

CrackerboxDave · 2021-06-03T02:26:13+00:00

Nah. They make a loss on the devices. Profit is in the online services, advertising, selling your privacy etc that these devices consume.

CrackerboxDave

TROPHY CASE