K
Kariem Hussein
As I am not sure on the terminology, here my assumptions:
xsn: compressed form template
xsf: manifest for uncompressed form template
xml: Infopath form
I am using Infopath 2007. For our solution, it is necessary to have the
form template in a version control system (subversion).
I found the great option of saving as source files (File > "Save As
Source Files...") in order to have the form template saved in a
directory outside of the compressed archive. This whole directory is in
version control now.
The version control system is also accessible via http, and the manifest
is accessible via:
https://server/svn/path_to_cool_form/manifest.xsf
In the form (resulting XML) I have to adapt the href attribute of the
mso-infoPathSolution processing instructions to point to the above URL.
When I try to open the file, Infopath will open it correctly after
retrieving the information for the form temlpate from the HTTP resource.
It even provides HTTP authentication ... Perfect so far
The problem is, whenever I save the form, it changes the href attribute
to match the publish location from the form template (publishUrl in
xsf:xDocumentClass of the manifest).
The publish Wizard only supports publishing to compressed form templates
and requires an additional manual step.
Are there any tips or better ways of doing what I just said?
Thank you,
Kariem
xsn: compressed form template
xsf: manifest for uncompressed form template
xml: Infopath form
I am using Infopath 2007. For our solution, it is necessary to have the
form template in a version control system (subversion).
I found the great option of saving as source files (File > "Save As
Source Files...") in order to have the form template saved in a
directory outside of the compressed archive. This whole directory is in
version control now.
The version control system is also accessible via http, and the manifest
is accessible via:
https://server/svn/path_to_cool_form/manifest.xsf
In the form (resulting XML) I have to adapt the href attribute of the
mso-infoPathSolution processing instructions to point to the above URL.
When I try to open the file, Infopath will open it correctly after
retrieving the information for the form temlpate from the HTTP resource.
It even provides HTTP authentication ... Perfect so far
The problem is, whenever I save the form, it changes the href attribute
to match the publish location from the form template (publishUrl in
xsf:xDocumentClass of the manifest).
The publish Wizard only supports publishing to compressed form templates
and requires an additional manual step.
Are there any tips or better ways of doing what I just said?
Thank you,
Kariem