When we have more than 5000 items in a SharePoint Online list which we need to display in a custom form, we can only display 5000 items in the form, and to display more than 5000 items we need to write a recursive ajax function using REST API.
So that it will concatenate the items in each recursion and then can be able to display more than 5000+ items, but each iteration/recursion pulls only 99 items out of 5000+ items at a time.

I have to recursively/iterate the piece of code 50 times to pull 5000 [i.e. 5000/99] items to display it in a custom form, and if the number of items is more than 5000 for e.g.: 100000 then the iteration of code would be 1010.10 times and so on i.e. Number of items/99

Consider a scenario where we have more than 1 lakh items out of which item in between 60,000 to 70,000 have inactive records which are not in use, which need to pull out, so you can imagine the pain in recursively pulling out 99 items in each iteration of code to reach to items between 60,000 to 70,000 or 100000+ items the scenario will be worst if we don’t know where is the inactive items resided in more than 100000+ records.

In a Scenario where there are complex transaction of more than a 100000+ of records to update and display then again it is a nightmare.

As per Microsoft the limitation is to improve the performance of the database and SharePoint

Hi All,

I have a customer who is about to walk away from SharePoint online as we can’t get the metadata of the version of the document into the footer. They’re going to go to livelink or docuware.

What’s the problem?

This may sound small but industry standard document management requires that footers of documents can contain metadata, most importantly the version of the document so when a user prints the document the document can have the correct controls embedded right the way through the document. It’s called Document Control.

SharePoint online allows us to create content types and, through a feature called Enable Labels, allows us to create a label and add an metadata to it. We can then add a template to the content type such as a Microsoft Word document and using the quick parts feature in Word add in the label that contains the meta data into the footer.

This worked perfectly in On Premiss SharePoint.

SharePoint online allows us to add metadata it just won’t recognise the version.

I have spent over a week working with Microsoft office 365 support analyst who needed me to give him a demonstration of what I was trying to achieve four days after contacting him he finally understands the problem and sends it onto the ‘specialised team’ I am then told Microsoft can’t do it themselves.

For a product that seeks to dominate document management and control this is absolutely a massive oversight.

I feel after dealing with Microsoft it’s kind of ‘it can’t be done and goodbye’.

I actually think the loss of this function is a massive deal and unfortunately a deal breaker for some

Thanks all

Tony

DITA authoring is used primarily for documentation, when multiple authors are working on different components, often with an approval workflow. It is very useful for producing agendas and minutes for government or board meetings, technical documentation of various sorts.
DITA environments have two key parts: a library of document "components", and a container for a "map" that collects and orders those components into a publishable document. The final product is output to various formats, typically PDF, e-Book or html.
There are already DITA authoring tools that use MS Word as the base authoring platform (Quark, DITA Exchange), because most authors are familiar with Word as a writing tool.
SharePoint provides almost all the functionality of a good DITA authoring environment EXCEPT for a reliable way of bringing components together in a "map".

An MS Word document's master/sub document functionality can (almost) provide the mapping ability - but it's clunky and unreliable.
If only the SharePoint dev team and the MS Word dev team could put their heads together and work this out. A Word master document in SharePoint that easily finds and links to sub-documents also in SharePoint, and reliably compiles as a single document with one set of styles, page numbering ToC, etc.