Combing five files with same content but different names into one file with versions in sp2019

I am working with SP2019 and On the file share, there is a Legal folder added which gets lot of files dumped into it. Once users work on files, they save it there and send it to external party for review, this file as an example be named as ‘General Accounting Assessment’ and post review it comes back as ‘General Accounting Assessment_V1’ and sits on the same shared folder as the original file.

This review process happen multiple times and that results into 4-5 files on the file share with below names: 1. ‘General Accounting Assessment’ 2. ‘General Accounting Assessment_v1’ 3. ‘General Accounting Assessment_v3’ 4. ‘General Accounting Assessment_v4’

Users initially save file ‘General Accounting Assessment’to SharePoint prior to sending out for review to external party so when v1, v2,v3 and v4 version file arrives, they manually rename the files to match it to name ‘General Accounting Assessment’ and drop into SharePoint so it can add up as a new version to the existing file.

I would like to automate this process and for which I am wondering if there is a way maybe by Flow or SharePoint to check whenever a new file is added, strip off the portion _v1 or _v2 or _v3 or _v4 dynamically appended at the end to file name ‘General Accounting Assessment’ and save it to SharePoint

Can someone please help on the proposed solution, thanks in advance.

Modern Team Site document library page in SP2019 does not show Exit classic experience option

I am working with SharePoint on prem 2019 and have a team site created in modern experience where several document libraries have been added. When site is accessed and document library link is clicked from quick launch, it opens up in modern UI. Once return to classic sharepoint is clicked, it takes to the classic experience. Once on the classic UI page, I do not see ‘Exit Classic experience’ link on the lower bottom left to go back to modern ui at all.

What could be the cause of this, can someone please assist, thanks in advance.

Can’t modify Managed Properties in SP2019 Search Service that was migrated

I’m having an issue with editing Managed Properties in a Search Service I migrated from SP2013 to SP2019, yes I bounced it through SP2016, with the DB attach method. I’ve run a full crawl in SP2019 but when I try to edit a managed property from Central Admin I get this error when I try to save the changes.

The settings could not be saved because of an internal error: Search has encountered a problem that prevents results from being returned. If the issue persists, please contact your administrator.

This is not a permissions issue, I’ve tried with several different accounts including the farm account and the installer account. I checked and I am able to edit the properties in SP2013, and in the SP2016 farm that i’m bouncing through.

SPFx web part throwing error in SP2019

I have created a web part by selecting option. I have tested this in SP Online which is working fine.

Now I have moved this .sppkg file to SP 2019 app catalog. While adding app to app catalog it is showing as below. It is getting content from SP Online. enter image description here

In write-manifest.json file I have left the default values

{   "$  schema": "",   "cdnBasePath": "<!-- PATH TO CDN -->" } 

Now I have installed the app to app catalog then added web part to the page. I haven’t modified the OOB web part which comes while creating the web part using yomen generator. I have selected React as framework for this.

But it is throwing below error after I have added web part to page enter image description here

Is this because of the write-manifest.json file’s cdnBasePath value?

Indexing lookup column in SP2019

I am working on a project where a document library is about to exceed threshold and lookup column is one of the metadata columns being used in the library, I am working with SP2019 on prem.

The lookup column i have does not allow multiple values selection and its the main column based on which I am looking to create an index. I referred this article by Microsoft and not sure if I should index lookup column or not.

Can someone shed some light on above, I can increase the threshold count but do not want to go that route. I was able to create an indexed column based on the lookup column, wanted to know if that is something I should be doing or not.

Thanks in advance.

Pages library missing from SP2019 Site contents

I am working with SP2019 and on Site contents of root site collection, I am not seeing Pages library. Both SharePoint server publishing and sharepoint server publishing infrastructure features are enabled, still weird part is pages library still not available under site contents.

Does anyone know the reason? On all the subsites, I see pages library under site contents but missing from top level site contents, sounds weird to me.

Can anyone help please, thanks in advance.