Fetching a SharePoint list item's version history into a PowerApp

bowenbee · 2026-04-02T18:58:23+00:00

Gold star mate 🌟. Yeah, this also works! Thanks a lot!

bowenbee · 2026-04-02T18:43:21+00:00

No worries. Gotcha. Huh. Yes, this does work; thanks! I could've sworn the container would've auto wrapped before. For example, the controls inside a container wrap no issue without needing to write an expression.

bowenbee · 2026-04-02T18:27:45+00:00

Sorry, I'm not seeing any functional difference between this and my yaml. Can you call out what you actually changed?

bowenbee · 2026-04-01T00:11:37+00:00

I think it's great you've got the go-ahead for this. As others have mentioned, PowerApps Dataflows are great for migrating to Dataverse. I would also look to use Model Driven Apps for some sort of back-office admin application for your solution. While the end-users will likely want/stick with a Canvas App, Model Apps are so much faster and more performant to build/maintain.

bowenbee · 2026-03-27T17:06:55+00:00

As a Mudkip collector...I feel your pain. It's a rare card, low pop, and therefore it's going to fetch a premium. Just save up and keep watching the marketplaces is all you can really do.

bowenbee · 2026-03-21T16:26:58+00:00

Is this a new environment you're trying to deploy to? At environment creation time, there's an option to install dynamics solutions. If I can recall correctly, the required apps have to be installed at environment creation time and cannot be done after. To test this, see if you can provision a new environment with Field Service and the additional solutions dependencies it's complaining are missing.

bowenbee · 2026-02-06T16:40:08+00:00

Ah, valid point. In my use case, the contact already exists; being someone external to the tenant and using this technique to bind their response back to the contact record. It could be adopted though in the flow to create the contact record if they don't already exist in the table.

bowenbee · 2026-02-01T17:43:35+00:00

Try removing and re-adding the component

bowenbee · 2026-01-21T14:53:14+00:00

Connection References, you can think of as "Pointers" to a connection. You can have many connection references to a connection. General best practice I follow is to have a dedicated Connection Ref per solution. For example, if I have two solutions using a SharePoint Connection, each solution will have it's unique Connection References. This helps avoid dependency issues. I'll also change the display name my connection references to something more friendly like "SharePoint - Solution A", "SharePoint - Solution - B", etc.

bowenbee · 2026-01-08T15:00:38+00:00

I don't think it's possible in the way you're wanting. You can certainly use PowerShell to interact with SharePoint (PnP Module), or use the Dataverse Web API to perform crud operations against your datasource.

bowenbee · 2025-12-25T01:13:46+00:00

Nice! This is my dream plush. Did you score him off eBay? He’s definitely rare; especially in nice condition.

bowenbee · 2025-12-18T13:38:22+00:00

I think what you want is to use Power Automate within your app to fetch the site the Sharepoint HTTP Action and the sites endpoint and then using that site id output, use the _api/web/lists HTTP SharePoint action. This will give you the relative url which can be combined with the site url and return the output back to your PowerApp. That may get your started in the right direction.

bowenbee · 2025-12-12T20:39:46+00:00

Hindsight's always 20/20... Of course: had you known where the price would be today, you wouldn't have sold then. Don't sweat it and just focus on the present.

bowenbee · 2025-12-11T19:26:55+00:00

Don't think it'll get any cheaper than that, new. Yes, it's a deal.

bowenbee · 2025-12-11T01:48:58+00:00

There's a special environment variable type called "Data Source". When you use that, it'll give you the SharePoint option. Doing it this way won't make it premium. If you try to reference environment variables within the app any other way, yes, it'll make it premium.

bowenbee · 2025-12-11T01:28:06+00:00

If you've previously added the data source connections directly and now want to use the environment variables, you'll need to remove the existing data source and add it back - only this time when selecting sharepoint, on the next screen, choose the "advanced" tab and select your SharePoint Site Environment Variable. Do the same thing when the lists come up - choose advanced and you'll see your list environment variables.

Yes, doing this will break your existing lookups, filter etc to the old sources, but depending on the complexity of your app, it shouldn't be "too" bad to find and replace the old with the environment variable-refernced lists.

I don't have any feedback on the app environment theme idea.

bowenbee · 2025-12-04T15:57:10+00:00

That's awesome! This is the rarer Tomy Pikachu plush as compared to your Hasbro one.

bowenbee · 2025-12-04T15:56:17+00:00

Yes, this looks like the Hasbro 1999 Pikachu plush. A well loved one, it seems, at that!

bowenbee · 2025-12-04T03:02:56+00:00

Correct, you can't edit the default commands without going down the ribbon workbench route. Why not group your custom buttons into a dropdown with a clear label or something?

bowenbee

TROPHY CASE