New answers tagged

0

This might fulfill your requirements (no javascript needed - OOB solution) : 1.Add a new field of type calculated to the list and set it equal to the start date field (your formula should look like : =[name of the start date field]) set the return type of the calculated field to Date time (Date only) 2.reivew the list data to check that end date is set as ...


0

You can save below code in a JS file in a document library and set that file as JSLink to End date field: (function () { // jQuery library is required in this sample // Fallback to loading jQuery from a CDN path if the local is unavailable (window.jQuery || document.write('<script ...


2

Override the PreSaveAction in order to cancel the save. function PreSaveAction() { if (confirm("Confirmez-vous ce choix de réforme ? : ")) { return true; } else { return false; } }


1

On your saveitem button click event call below method $(document).ready(function(){ $( "#ctl00_m_g_9ff78e92_ed40_4212_ae0f_44b787664fa8_ctl00_toolBarTbl_RightRptControls_ctl00_ctl00_diidIOSaveItem" ).click(function() { /*var isConfirmed = confirm("Confirmez-vous ce choix de réforme ?"); if (isConfirmed == true) { ...


1

I am not able to add a comment hence writing in the answer section. There are 2 scenario which you should verify. Scenario-1: Go to "File-> Publish" and verify your target library. Scenario-2: Verify your data connection once because there might be wrong target specified there. Let me know if above scenario defines your problem. Thanks


1

if (_spPageContextInfo.serverRequestPath.contains("DispForm.aspx")) // View form if (_spPageContextInfo.serverRequestPath.contains("EditForm.aspx")) //Edit form if (_spPageContextInfo.serverRequestPath.contains("NewForm.aspx")) //New form You can try replacing contains with endsWith(), it should work better. ExecuteOrDelayUntilScriptLoaded("SP.js", ...


0

I just had this error. One thing I have learned about SharePoint, InfoPath, and Nintex is that if you get an error, it is usually something very simple and small--it just requires a little energy to dig it up. What the cause was in my case was I had created a field in my InfoPath form. (I forgot to look to see if it actually showed up in my list ...



Top 50 recent answers are included