| Sharepoint Developer at Remote, Remote, USA |
| Email: [email protected] |
| JD: Needs someone experienced with both on-premise SharePoint and SharePoint Online Need help upgrading SharePoint 2013 to SharePoint Subscription No support from Microsoft for SharePoint 2013 platform to perform upgrade, can only provide shoulder surfing at best Data on current old platform is mostly NERC-CIP/BCSI, which should be treated carefully during upgrade Resource needs to know best practices/procedures for handling BCSI data in the Cloud Meetings to discuss NERC-CIP/BCSI access continue for both on-premise and Online environments Process to build out preventing inadvertent access in ServiceNow/CyberArk/etc. SharePoint Online development Lot of sites broken after migration Version History - Not migrated from SharePoint 2013, have to be turned on manually for each document library in question. Each version takes up space on the overall M365 tenant Need re-organization of site collections into proper "Hubs" After migration, Microsoft recommends to restructure into new standards Need redevelopment of workflows into Power Automate Workflows migrated, but will depreciate in April 2026 Need redevelopment of InfoPath forms InfoPath forms are depreciated and couldn't be migrated to new platform. Have to be rebuilt using Power Automate Experience with Power Automate/Power Apps New requests on new platform come for site formatting/workflows/APIs/custom scripting Need redevelopment of site page formatting i.e. lots of sites broken due to custom HTML/CSS/JS on old site which doesn't work on new platform For example, IT POD page uses a lot of custom JS/HTML which needs to be rebuilt using SPO standards Lists/list views migrated broken Needs time on a case by case basis to fix each list and each list view to view the data properly Need person experienced with PowerShell on SharePoint Online platform. Lots of functionality exists on PowerShell, not available on GUI Currently supporting 3 separate SharePoint environments Commercial (PSEG1.com tenant), GCCH (pseg.sharepoint.us) and old on-premise SharePoint More commercial usage due to ProofPoint file sharing/JAMS,etc./email not being a viable option Until procedures/approval to use GCCH external sharing is implemented, commercial tenant will have to be used No tentative timeline when this can be implemented Needs better understanding of GCCH tenant constraints Lots of Microsoft apps do not work on GCCH tenant, have to work within those constraints Old SharePoint 2013 still needs to keep running to support NERC-CIP/BCSI data No longer officially supported by Microsoft since April 2023 Will need to be upgraded to SharePoint Subscription -- Keywords: javascript information technology Sharepoint Developer [email protected] |
| [email protected] View all |
| Tue Oct 29 00:07:00 UTC 2024 |