New answers tagged custom-actions
2
Here is some js that should load efter the ribbon is loaded:
SP.SOD.executeOrDelayUntilScriptLoaded(function() {
// Your code here
},
"sp.ribbon.js");
More about modifying in this blogpost
Edit:
// Fires ‘ribbontabselected’ after the ribbon has been initialized after load
ExecuteOrDelayUntilScriptLoaded(function () {
var pm = ...
0
Here is what I do that I create a field called 'IsSubmitted' on the form ,when submitted I set IsSubmitted=true.
Now publish the form in the form library.Before that also create a submit data connection to the particular library.Now from form librarry settings create the workflow (trigger it when new item is created).
0
I solved the issue having the following url:
<UrlAction Url="javascript:function GoToUrl(){var site='{SiteUrl}';var item='{ItemId}';var list='{ListId}';window.location.href=site+'/_layouts/Pages/InterPage.aspx?list='+list+'&ID='+item};GoToUrl();return false;"/>
0
After some investigation i understood the issue, it seems that the editcontrolblock is rendered by javascript and basically server side you can't do much. And there is no way doing that.
Hope this helps someone in the future!
1
I resolved my issue by using EnabledScript property in Custom Action.
I verified whether current list is my custom list and enabled the button. For the rest of the lists the ribbon button will be shown but disabled.
I referred this link.
0
It is hard to scope a Custom Action more than on a content type I am afraid. Is javascript in a content editor webpart on the page that displays the one list an alternative?
See this link for all information regarding different registration types for Custom Actions http://blog.alexboev.com/2011/12/registrationtype-registrationid-in.html
0
You can do this with SharePoint and SharePoint designer 2010.
Without being able to post pictures all I can really do is refer you to a great tutorial I just went through myself.
Pay attention to the use of custom new item form web part, web part parameters, and then using Javascript to call the NewItem2 method to pass a parameter to the NewItems.aspx ...
1
It looks like it was a simple caching issue. Clearing the browser cache solved the issue.
Top 50 recent answers are included
