11
Earu
9d

So I've created this account specifically for this rant. I usually just browse anonymously.

I've recently been hired in a big company that is one of the biggest Microsoft users in the world and my essentially revolves on making it easier for our collaborators to work with SharePoint (and other ms software)

Never in my life have I hit that much of a roadblock. So for the past week I've been trying to integrate what Ms calls webparts. And to modify the default webparts Ms provides you need to their properties (or Metadata). Except here's the big problem these are NOT documented anywhere (unless I failed to find it, if you do know where it is documented please HMU), so I've found myself trying to reverse engineer the js scripts that are served with SharePoint to figure out what the webpart properties are called and what type of data they are! I've been going through endless github repos using the CSOM nuget package (it's the library everyone uses to interact with SharePoint) and I finally found out about this other library called PnP which is a wrapper around CSOM that makes it easier to use. That wrapper has a way for me to load existing page and look at the properties of existing webparts. So here I thought it was the end of my suffering and I could finally get an idea of what it should be. Turns out this method doesn't work because one of the dependencies it has has had breaking changes and they still updated it even though it breaks their code! So for the past two days I've been trying random combinations of key values with different data types and json serialization methods.

Oh and yeah I've also looked at all the http calls via the chrome network tab, the metadata is not served as an individual file but is computed by Ms servers when they're serving you their html files.

So uh yeah run from CSOM if you can..

Comments
  • 2
    That entire model was deprecated some time ago. They went to an entirely js+rest model and no longer allow deploying code to the server. This was done to enable it to be a viable cloud offering.

    If you plan on sticking with SharePoint as a career path (do not recommend), you're going to want to pick up Angular and typescript. They have a react option, but the component library they use is barely functional in it.
  • 3
    Well I'm already familiar with typescript and react, it wasn't exactly my choice to stick with SharePoint as you may have suspected. Time will tell if this is going to last I guess...
  • 4
    @Earu
    Blink twice if you're a slave being forced to work and we'll send a UN committee to deliberate on how best to rescue you 😋
Add Comment