I am working on SharePoint office 365 (2016), and facing issue while adding custom validation in new item form.
Here scenario is complex, I can't handle by using Validation setting/formula. So I have choose custom JavaScript code.
As validation should be perform on click of Save button and PreSaveAction method successfully called but only in 'Classic Experience' but when user changed to 'New Experience' it won't call because of change of HTML structure of the form.
Does any one have an idea how to fix this issue?
Thanks in advance!
As stated in the documentation here jslink is not yet supported in the new experience. In order to support your customization you'd have to disable it.
Related
I´m new to the addins, just want to perform a simple task as creating a button with a link in the taskbar that opens a browser and that´s it.
So far created the project based on ms tutorial and everything is working great (with fixed certificate problems).
To my understand this should be as easy as to create a button with an ExecuteFuncion actions mapping to a javascript function with a window.open
e.g.
function windowOpen(event)
{
window.open("https://www.microsoft.com");
event.completed();
}
Thanks for the help,
Regards,
André
For security reasons, Outlook does not support window.open directly inside of Add-ins. To open a window in an Outlook Add-in you can use the displayDialogAsync API (documentation here.) We recommend this guide to understand end-to-end usage of displaying a dialog in an Add-in.
For SharePoint 2013 blogs alert me, I need to develop a custom form with less options as shown here. Another reason to go for custom form is better UI.
Current thoughts:
1. Develop a dynamic form using Bootstrap as user clicks on custom alert button
2. Using JSOM to make an entry in alerts
Question - Is it possible to make entry using JavaScript?
My research till now:
http://sitename/_vti_bin/alerts.asmx doesn't have add/update methods.
It has just view & delete methods.
One of the blog published in 2013 says alert doesn't support Client
object model.
http://www.learningsharepoint.com/2013/09/17/client-object-model-doesnt-support-creating-sharepoint-2013-alerts/
Technet Discussion
https://social.technet.microsoft.com/Forums/sharepoint/en-US/43d801d4-0e89-4ec5-9d6c-b36f8106fc0d/how-to-create-and-delete-alerts-using-client-object-model-or-even-web-services
Learn about Alerts
Alert web-service
https://msdn.microsoft.com/en-us/library/bb249933.aspx
Alert methods
https://msdn.microsoft.com/en-us/library/websvcalerts.alerts_methods
Calling web-service using JavaScript
https://weblogs.asp.net/jan/calling-the-sharepoint-web-services-with-jquery
Conclusion
From above data, it doesn't seem possible to achieve custom form for alerts using CSOM.
You need to use Custom Action to hide or overwrite the default ribbon button Alert Me.
Create an Application page with you custom logic/forms and use a new Custom Action to Show this forms
I am migrating MOSS 2007 site to sharepoint 2010 without UI upgrade. I noticed that document library action tab includes menu called "Edit in datasheet". I need to know how do I hide it from ONLY document library. Please Help.
Another solution. Document Library settings->advance settings-> Allow items in this document library to be edited using the datasheet? = N
A possible way is to edit the Display form for the library DispForm.aspx using Sharepoint Designer and use some client side code (Javascript/Jquery) to hide the button.
If you have access to jquery something like this will do:
$(document).ready(function() {
$("[text='Edit in Datasheet']").remove();
});
Check this article for more details
i am working in sharepoint 2007. i want to open the newlistform.aspx using modal popup. before that i worked the samething in sharepoint 2010. sp2010 having sp.ui.dialog.js file, but moss2007 dont have this file, is it possible to access, if yes please help me to resolve this.
Thanks and Regards,
Rasu.U
No, the dialog framework was first introduced in SharePoint 2010. If you want something similar you will have to code it yourselft using fancyBox or something like it.
We're implementing SharePoint 2007 but have Office 2003 as our client. This causes problems when editing metadata since custom field types like BDC columns aren't represented properly within the Web File Properties dialog in Word. To get around this, we would like to disable the this dialog to force users to edit metadata within SharePoint.
How can we do this? Also, are there other alternatives that we should consider (short of upgrading to Office 2007)?
We use a product called metaEngine to customize the Office properties dialog. (I have no affiliation with the company)
Essentially it uses an httpModule to detect when the Office properties dialog is called and injects / rewrites the html to provide a custom editor for metadata. You could either use this approach, or use a similar httpModule to present a "this functionality is disabled" type screen.
Have a look at the requests going between Office and SharePoint using Fiddler and it'll give you an idea of what you could change.