Hi there,
Is there much of a difference between customising a LIST form using infopath to alter layout and so forth, vs changing things via altering the "Form Web Parts" for the three forms (new, edit, view)?
I'm interested in "the works", so:
- functional issues - obviously you can control rules and add code, and its perhaps easier or more idiot proof to customise format and layout in infopath, but are there any big "don't use infopath if you are trying to do this" or vice versa?
- deployment issues, is there a way to "keep" the customizations I make in a form with the list to move to another site - are there any gotchas? ie: can you include (either or both or neither) infopath or aspx forms in a feature/solution ?
- is there any tricks to the infopath forms as I noticed that at least in some lists, the "default" forms are in the list and the infopath forms are actually in "\Forms\" although some of my forms this location seems to be "Announcements" (assuming this is an Announcements list customisation).
- does the form customisation have any impact on Workflows or anything other than the list its applied to or is it safe to change these things without unwanted flow on effects?
Other recent topics
