skip to content »

Updating site content type failed infopath

updating site content type failed infopath-9

or check for network speed if it is slow enough to increase the publish time more than 30 sec, switch to higher network speed.

updating site content type failed infopath-61updating site content type failed infopath-13updating site content type failed infopath-35updating site content type failed infopath-69

Separately I've found that most form libraries with issues on publishing form templates, all seem to have multiple files in the library and many different files that are unlinked from the current template.This site collection should be dedicated to creating and publishing content types.Content Type Publishing Hub allows Share Point administrators to have a central location where they can manage and publish content types from across all their Share Point web applications.The production environment has the column created from the powershell script.We then publish the Info Path form and connect the column from the form to the newly created column.Info Path is used to capture information and my work around is to reduce the information displayed. If you create a new form library, you should not have any issue publishing the form for the first time.

You will be able to add all of your columns and publish the complete form.

The end user will still continue to see a single giant list.

Here's the breakdown of what you can have in a list can have: 64 Single line of text and Choice (drop-down menu or radio buttons)31 Multiple lines of text and/or Choice (check boxes (allow multiple sections))32 Number and currency32 Hyperlink16 Date and time16 16 Yes/No8 Calculated Note: The number of shared data types are not 64 Single Line of Text and 64 Choice.

This allows us to have one Info Path form that can be published to more than one site.

We create the columns by manually adding the column through the Share Point screens as a site column and then add it to our content type.

I haven't tested if linking all the files back to the current form template will resolve the issue or not, but it was something I noticed when recreating the form library.