Ask a questionAsk a question
 

AnswerUsing InfoPath as content types

  • Thursday, November 05, 2009 9:57 AMaaroh_bits Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi all,

    I have a requirement where are all the IT documents will be stored centrally in something called as "IT Document Center".
    Few departments have word templates (already done) where as other departments are using InfoPath templates (creating issues) .  

    This is following structure:
    http://testserver/it/AllDocs/Operations/<<AllInfoPaths templates here>>
    Here, for Operations departments, I have published 8 InfoPath forms as templates


    Now, in other applications we have a sections called as tools for different departments (IT, Finance, etc.) with following URL:

    http://testserver/tools/<<here other tools for different departments including Operations>>
    Now, I need to use Content Types for 8 templates which are centrally stored in "IT Document Center".

    Problem is that, I am not able to create content types of InfoPath forms in "tools" sections.
    In general, how can I refer InfoPath forms which as stored in  "IT Document Center" in "tools" site.

    Can somebody please advice me on this?
    Thanks in Advance.

    Cheers,
    --aaroh




Answers

  • Friday, November 06, 2009 2:51 AMClayton Cobb Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    What I said above applies directly.  You shouldn't be storing your InfoPath content types or form templates way down low like that.  You need to put them at the site collection root so that every site below that can use them.  Sites at the same level cannot share information.  It has to be on a higher site so that it inherits downward.  So, at a minimum, you would want the content types and form templates saved at the Asia level so that they can be used in Tools or IT.  It doesn't make sense to store templates at a lower level - that is probably something that should be reviewed by the team, because it sounds like they have mistakenly decided to do this in an arbitrary area that in no way makes the files reusable except for in the sites that are below ITDocCenter.

    Also, form templates can't just be uploaded and used.  They must be published as a content type, and during the content type publishing process, it asks you for a place to physically store the document within that site where the content type is being made.  That's why you publish it as a content type at a higher level.
    SharePoint Architect || My Blog
    • Marked As Answer byaaroh_bits Monday, November 09, 2009 5:30 AM
    •  

All Replies

  • Thursday, November 05, 2009 1:32 PMClayton Cobb Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I don't understand what you're saying with the tools section.  What are you trying to do exactly?  Is "testerver/tools" not a SharePoint site?  You said "in other applications."  Why would you need InfoPath content types (a SharePoint-only concept) in two separate places on your Intranet?  InfoPath form templates should only be published to one place, and they can only be published to SharePoint.

    If you are saying that testserver/tools is a SharePoint site but is a separate site collection or a higher-level site in the same site collection, then publishing your content types to the Operations place is of no use.  Content Types only inherit downwards.  If you save them all at a lower level, then you cripple yourself, because they are not usable at higher levels.  You are supposed to create content types at the top-level of your site collection so that all sites within that site collection can leverage the content types.
    SharePoint Architect || My Blog
  • Friday, November 06, 2009 2:30 AMaaroh_bits Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi Clayton,

    Let me explain my case elaborately.
    We have a site collectio n called as http://comanyname/asia

    Under this site collection we lot of sub-sites and in my case, I am dealing with 2 sites namely IT (site) and tools (site) are on the same level .

    http://comanyname/asia/it
    http://comanyname/asia/tools

    IT has few sub-sites for different departments (Operations, Security) and central documents for all IT documents namely IT Document Center

    http://comanyname/asia/it/ITDocCenter
    In IT document center, all departments have their document stored. (word or InfoPath).

    Operations dept. uses InfoPath and I have published all their documents in http://comanyname/asia/it/ITDocCenter
    We have one more site called as tools.

    I have developed a solution where in tools sections , Operations people can enter their checklists on regular intervals such as Daily, Weekly, Monthly, Yearly etc.

    For this, I need to have content types which will refer to ITDocCenter (http://comanyname/asia/it/ITDocCenter).
    But, I don't know how can I refer InfoPath templates as tools is different site and my InfoPath templates are stored in different site (IT).

    Can you please advice?

    Thanks,
    --aaroh



      
  • Friday, November 06, 2009 2:51 AMClayton Cobb Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    What I said above applies directly.  You shouldn't be storing your InfoPath content types or form templates way down low like that.  You need to put them at the site collection root so that every site below that can use them.  Sites at the same level cannot share information.  It has to be on a higher site so that it inherits downward.  So, at a minimum, you would want the content types and form templates saved at the Asia level so that they can be used in Tools or IT.  It doesn't make sense to store templates at a lower level - that is probably something that should be reviewed by the team, because it sounds like they have mistakenly decided to do this in an arbitrary area that in no way makes the files reusable except for in the sites that are below ITDocCenter.

    Also, form templates can't just be uploaded and used.  They must be published as a content type, and during the content type publishing process, it asks you for a place to physically store the document within that site where the content type is being made.  That's why you publish it as a content type at a higher level.
    SharePoint Architect || My Blog
    • Marked As Answer byaaroh_bits Monday, November 09, 2009 5:30 AM
    •