Tag Info

New answers tagged

0

On the NewForm.aspx add a Script Editor Web Part (from Media and Content) and add the following script: <script type="text/javascript"> window.location.replace(http://theListUrl/MyCustomNewForm.aspx); </script> But be careful. If you do, the only option to get it back to where it "normal" is to edit the NewForm.aspx in SharePoint Designer: ...


2

To create a form that would submit items to multiple lists, you should: Add some elements to your main list form, probably arranging them in a certain way. If those elements aren't related to fields as I suspect from your description, best way to do it would be to leverage OnPostRender CSR event and then use HTML5 selectors or jQuery to insert your HTML ...


0

I have experienced this issue several times on different farms. After some manipulations with the workflow using SharePoint Designer or a web browser, occasionally, it started to be impossible to open published workflow. The others workflows continued to work as expected, whereas when I tried to open the one that started to misbehave it showed the following ...


0

You could insert a Content Editor Web Part (CEWP) into the page and then create and upload a css style sheet where you assign attributes to the classes/parts you want and use "!important" -parameter on the attributes if they don't work. Example below: .class-name { attribute: value !important; } Then just enter the CEWP toolbox/options menu and ...


3

in your page make sure there is no reference to core.css.... issue is due to masterpage which has that reference that the page your using could be referencing the masterpage. several methods: 1) if its referencing a masterpage than make a custom masterpage that is almost the same only that it doesnt contain the core.css reference. 2) within your css add ...


0

I found a working Solution: First I decided to show the DropDowns (the simple ones - generated from the SPServices). On the page they are autofilled as they should be. Still the original Complex DropDowns were not populated with the data. Then I desided to manually select (despite already being selected) data in these Simple DropDowns. What happened was ...


1

The good thing with using ASP.NET is you can write your own logic and customize it whenever needed with much flexibility. It is relatively difficult than using InfoPath as we have to be concerned about the page life-cycle a lot. Also you can manage it easily with asp:view controllers when a large amount of components are there. (In your case 300) But on the ...


1

I am not involve in IP form designing but i know one of our department create IP form with tons of fields which slow down their site collection. Personally, As we know, this is last version of IP so i think better to design in ASP.net or access form. Check this post, they discuss couple of limitation. Disadvantages of implementing InfoPath in SharePoint ...


0

I figured it out--in SharePoint Designer for the List there's a section called Custom Actions: Thanks anyway :)


0

In addition to customizing List Views & Forms via XSLT, with SharePoint 2013 was introduced a Client Side Rendering (CSR) technique. As an introductory please follow this article Introduction to Client Side Rendering in SharePoint 2013. Since CSR is the default rendering mode in SharePoint 2013, I would recommend this approach to customize a New Form ...


0

You can create an Infopath form using the Email template that will embed the form into the email so the user doesn't require the Infopath client. Then create a submit button to help apply validation and fix the email address that the form will be submitted to. In your SharePoint library, go to the library settings and configure the library to accept ...



Top 50 recent answers are included