Forum Discussion
Question: Custom Webpart for Project Site
Hi tayram ,
It sounds like you have built a nice solution but I understand the optimisations you are trying to achieve. A custom web part (SPFx etc.) would be able to dynamically get certain properties so it should work fine in a template. One question though, why don't you just use the lists on the Project Sites for the registers /log (Submittals, Change Orders, Requests for Information, Purchase Orders)? That way everything would be associated to the project automatically and take advantage of the out the box access model. I guess on the "master lists" at PWA level, you have to have item level permissions so users can only edit the list items for the projects they have access to or can all users access / modify all list items on the master lists?
Paul
Paul,
Absolutely appreciate the reply. (Although, I should also say that I appreciate your years of wonderful content, across forums and your blog. You have been a vital asset to my personal explosion of knowledge of PWA, Power Auto, REST, Odata and all the fun stuff, so thank you!)
"Why not use lists at the Project Site level..."
My mind keeps going to this ideal. My main concern is breaking our custom PowerBI (not my strong suit) report, and creating a cascading clean-up for myself. Yet, using Power Automate to write the Project Site-level lists upwards to the PWA-level 'master lists' seems like it would fix much of this issue. There are 1-2 other concerns with making this move, but they aren't coming to mind at the moment.
"Item level permissions..."
This is one of my biggest concerns with developing the aforementioned webpart, and currently a topic I am digging into for possible solutions... without making Project Permissions (and adding the same folks to the Teams Team) an even more cumbersome process.
I have thoughts of completely overhauling our current PWA configuration for permissions & the resource pool itself... but first, I have to get onboarding alignment with HR and IT! Switching to Sharepoint Permissions Mode might actually fit us better once I move more to a PWA platform that is focused on the Project Site (and Teams), rather than half of everything occuring within the classic PWA PDP framework.
On another note...
I came into my current role (inherehited "what is") without any background in MS Project, the Admin side of SharePoint or the Sharepoint Framework... yet, after a year, I am starting to see that the choices, and expensive customizations made before my arrival, have almost locked us into an out-dated box. At this point, I see my goal on this front as trying to put us into a bigger, better framework, without breaking too much of the connective tissues that I do feel is important & functional.
I've brought up the possibility a few times, with our COO, about potentially reaching out to you for consulting purposes. Your reply here only reinforces this ideal. What would be the best way of getting the ball rolling with contracting your services on the consulting front?
Much appreciated,
TRHello PWA_Service ,
It's great to hear that you have found my content useful over the years - makes it worth while, thank you.
I understand the Power BI challenge with querying lists across sites but there are solutions to that challenge. Using the lists and libraries on the Project Sites would keep your solution simple - probably all out of the box, minus the reporting side of things.
I'm not sure I would switch to SharePoint permission mode - not unless you are happy to manage the team members access to each project site manually?
The thing to also consider, depending on your project management requirements, have you considered Microsoft's latest project tool - Project for the web? Project for the web alone wont meet your requirements due to the registers / logs, but building an app in Power Apps might?
I'm happy to have a chat about how I might be able to help you / point you to a Project partner who can etc. I'll drop you a private message regarding that to keep this post focused.
Paul
