According to my research, Lookup column does not support cross-site collection query in SharePoint, it is by design.
Howerver, Lookup column supports cross-subsites under the same site collection. For more information, please see "How to Create a Lookup Column to another SharePoint Site?".
It was resolved by re-registering the alerts, for reference please see point no. 9 in the below link:
Please check as following:
Will the same user be alerted in list or library?
When you set an alert on a specific file instead of the entire library, is it effective?
Does the alert setting only have no effect in the migration library?
Please create a new library in new server, send alerts on single file or entire library to multiple users to compare the ...
@Jimas has suggested a good solution for testing an upper boundary, but in addition to his well-informed and detailed suggestion, I also Believe you should test the lower boundary of your list threshold issue.
I have encountered this very issue myself, on-prem - with a different version of SharePoint some years ago. It had nothing to do with ...
From my experience, exceeding the list view threshold means, basically, 2 things.
that the results are more that the list view threshold
that sharepoint takes a long running query to iterate over a large dataset, which transaltes in time consuming queries and if the entries are over a limit, SQL Server might enforce a lock on the table.
These are the basic ...
All Excel-style expressions begin with an equal (=) are only available in SharePoint Online (not in SharePoint 2019).
In SharePoint 2019, you have to use the Abstract Syntax Tree (AST) expressions.
So try using below JSON:
Could it be something as simple as having your users look at the overlay calendar to see what's available, but when they want to book something, click on the specific room's calendar & then add the item?
I believe you can use @pnp/sp/profiles
Gets properties for a specified user
const loginName = "i:email@example.com";
const profile = await sp.profiles.getPropertiesFor(loginName);
As per my knowledge, this notification is harmless and can be ignored. Generally, the timer job will be executed on weekly basis. Your retention policy will still be applied to the library and work normally after then.
Below are the advantages of the SPFx webpart:
Capability to create Responsive UI using Office UI Fabric
With the SPFx solution, the user can experience responsive property pane, in ...