Hot answers tagged

3

Regarding the error you are receiving, if you are using different regional settings than English in your site, try to replace all the commas (,) to semicolons (;). You could make a easier calculation to. This one returns the number of days, hours and minutes between the 2 dates. =TEXT([Fin Diag]-[Debut Diag];"d:h:mm") Update Tried out your calculation ...


2

Each list keeps its own IDs and you will not be able to keep them perfectly in sync. Create a helper columns and let the workflow copy the ListA ID into that field, then refer to that field as the common ID. If you use the workflow step "Create item" instead of copying an item, you can transfer any field value from the current item to the new item, as ...


2

You can perform this activity using CAML query with the below logic Get the list items in descending order Set row limit as one and retrive the record CAML Query: <View><Query><OrderBy><FieldRef Name='ID' Ascending='False'/></OrderBy> <Where> <Eq> <FieldRef Name='Title' /> <Value ...


2

You can use a couple of approaches: Save last item id in SPList properties and then retrieve the value next time you're adding an item: //set - after setting all field values and updating the item itemAdd.Update(); wayList.RootFolder.SetProperty("LastItemID", itemAdd.ID); //you need AddProperty if it doesn't exist //get //then subtract 1 if needed var ...


1

I don't think there is something OOB for multiple columns. I would suggest to use JavaScript and override PreSaveAction to prevent the save if the combination exists. Something like that : function PreSaveAction(){ //get field 1 value //get field 2 value //perform a query to check if there are items that matches criteria if(noresults) { ...


1

This is because of security setting of SharePoint.Source All you've to do is: add the OnClientClick to the button's event, _spFormOnSubmitCalled = false;_spSuppressFormOnSubmitWrapper=true; <asp:Button ID="btnExportToExcel" runat="server" Text="Export to Excel" onclick="btnExportToExcel_Click" OnClientClick="_spFormOnSubmitCalled = ...


1

We were facing the same issue, we solved this by changing the following parameters (Power Shell). In our case, it was caused by very large workflows processing in parallel. ServiceBusTopicSizeQuotaInBytes: Set-WFServiceConfiguration -ServiceUri "https://workflow-service-url:12290" -Name ServiceBusTopicSizeQuotaInBytes -Value 18737418240 ...



Only top voted, non community-wiki answers of a minimum length are eligible