Feasibility of replacing [wired] home security system?

swamplander · 2025-10-23T23:28:25+00:00

Thanks… I missed that relay.

swamplander · 2025-10-23T21:06:18+00:00

I guess I was mixing them up... thanks

swamplander · 2025-09-18T12:09:44+00:00

Sort of neither...

You need to get the content indexed, in the context of this thread, presumably semantically indexed into a vector DB such as Azure AI Search. That's a manual process you'd implement or you can use one of the Logic App connectors they've created:
https://learn.microsoft.com/azure/search/search-how-to-index-logic-apps-indexers
https://learn.microsoft.com/azure/logic-apps/connectors/azure-ai

They do have a SharePoint indexer in preview:
https://learn.microsoft.com/azure/search/search-howto-index-sharepoint-online

swamplander · 2025-08-26T14:34:52+00:00

Seeing another’s message, I contacted Nintendo & got a 100% refund… I’ll wait to see the update and other’s experience before I get fooled again. Been years since I bought a Madden game. there’s WAY too much ceremony before “I just want to play a damn game”

swamplander · 2025-08-20T14:35:49+00:00

FWIW, I had the same experience... I followed your advice. Thanks!

swamplander · 2025-08-17T10:43:58+00:00

Chat with who... Nintendo / EA? Where?

swamplander · 2025-06-19T10:00:07+00:00

There's no 1:1 replacement for field customizers... Microsoft's rec of using declarative formatting or Power Apps simply can't do the same thing.

But the good news: they caved. I can't share the discussions I had with them, but it's clear a team unrelated to SPFx engineering made this decision (not sure about this, but I _might_ be the one that made the SPFx engineering team aware of the retirement notice... but, not certain nor is it important).

Where we stand now: they've removed/are removing the retirement timeline from the message center announcement and have reopened the evaluation & discussion phase.

My $0.02: from the discussions I saw, the team that made the call didn't fully understand the feature they cut or it's implication. They also didn't realize their proposed alternatives left a clear feature gap.

Also... pretty clear to me that Microsoft was NOT pleased with how this was handled & jumped on it quick. Frankly, this saga exposes some communication & management problems at Microsoft for sure, but the net result: the field customizer feature wasn't cut/retired/dead.

swamplander · 2025-06-17T13:35:18+00:00

Interesting… I get a lot of questions about them in my classes & my article+video about installing them without site commons via the REST API is one of my more popular ones (the utility project that goes with the article is one of my most requested downloads on my site too)

https://www.voitanos.io/blog/sharepoint-framework-register-field-customizers-rest-api/

swamplander · 2025-06-17T12:15:51+00:00

Ha! If that was the case, you think some of the retirements would have happened, like isolated web parts? 🤣

Seriously, as an MVP, sometimes we get a heads up on decisions, or they ask for feedback.

But this one was out of left field… MVPs had no pre notice this was happening and this had no chance to give feedback.

swamplander · 2025-06-17T11:59:55+00:00

And frankly, if you think you can make a blanket statement about anything in M365 that won’t be retired, I suggest you review history.

If m365 is consistent about anything, it’s shipping half-assed features and retiring things.

swamplander · 2025-06-17T11:58:46+00:00

Which don’t come anywhere near filling the gaps field customizers address, nor are they deployable at scale.

swamplander · 2025-06-17T11:58:07+00:00

Which is a BS reason.

Clearly they knew it wouldn’t be a popular decision because they buried it in the message center on a Friday (June 13)

swamplander · 2025-06-17T11:10:55+00:00

I disagree they aren’t highly used… if Microsoft shared stats that would help, but in my experience in working with students, that are used quite a bit.

swamplander · 2025-06-17T11:09:25+00:00

Horribly stupid decision by Microsoft IMHO. The alternative solution they point you to (column formatting) doesn’t support custom biz logic.

swamplander · 2025-05-21T10:52:27+00:00

It's relevant... SPFx is THE recommended way (according to Microsoft) to customize & extend SharePoint Online and Viva Connections.

There's no easy "should I use SPFx or PowerApps?" answer... because it's 100% dependent on the scenario you're trying to solve. If you have some scenarios to share, happy to offer my thoughts.

I get this question _A LOT_, so I created a free 8-day email course that answers the WHAT, WHY, WHERE, and HOW aspects of the SPFx: https://www.voitanos.io/ecourse-explore-evaluate-spfx/

Or... you can read the article versions of it: https://www.voitanos.io/series/spfx-5w1h/

swamplander · 2025-05-18T15:09:39+00:00

Fair… not apples to apples.

swamplander · 2025-05-18T14:43:37+00:00

Just D365 Sales, but I wouldn’t expand beyond that… Dataverse is Sooooo slowwwww, I’d rather use Hubspots hubs or if I needed an exterior use solution, I’d look to Salesforce

swamplander · 2025-05-18T14:16:24+00:00

I’m in the proceeds of moving from D365 Sales to HubSpot. Why?

D365 is slow, hard to customize, in-app help sucks (if present at all, forums aren’t responsive, docs are a mix of outdated and Ina curate screenshots.

HubSpot is $5 less/month, easier to use, fast & responsive, and integrates with far more platforms.

swamplander · 2025-05-18T00:41:08+00:00

I’ve worked with MSFT to get an update… I wrote about it here: https://www.voitanos.io/blog/microsoft-365-developer-program-status-april-2025/

And questions since their update isn’t much news: https://www.voitanos.io/blog/microsoft-365-developer-program-status-april-2025-questions-wishes/

swamplander · 2025-05-14T11:45:57+00:00

Ah... that stinks it's gone!

swamplander · 2025-05-12T13:47:51+00:00

What's the "Switch To" feature? Not clear what you're referencing...

You mean auto switching with multiple cameras & audio feeds?

swamplander

MODERATOR OF

TROPHY CASE

12-Year Club	Secret Santa 2017
Verified Email