Forum Discussion
Managed Metadata Field
Given that this type of field isn't supported in Access, and can't be reliably used, my suggestion would be to avoid it entirely for the purposes of your Access relational database application.
This is part of a larger pattern, IMO, in which SharePoint lists are a world unto themselves. We can't reasonably count on them outside of that environment. If you stick to SharePoint, of course, they're fair game.I actually like the idea of SharePoint lists as a backend for some specialized Access solutions because of the fact that you can use them off-line as well as while connected, and because they are reachable via an internet connection from multiple locations.
That said, and repeating myself, because of their unique internal construction, I would avoid any but the basic datatypes like numbers, text and dates.Your experience may vary, but that's how I see it.
Reza Domani has some excellent videos on PowerApps.
I have a lot of those but no longer use them because the flows that run them constantly get turned off. Again....???????????????????????
I'll check out your video.
Tx Geroge. Cheers
- Yes, they have some great content!! THEY should work with Microsoft to get info and PnP out in a more user friendly manner. Everything needs to be a week of research just to pul off one workaround or hack since the tech has overlookedonpourpose functionality. Do I sound like a broken record? Just figured, the squeaky wheel gets the grease.