S
Shane
Platform: SharePoint Portal Server 2007 Enterprise
Word Version: 2007
InfoPath Version: 2007
This seems to be an issue for alot of people. Basically what happens is:
1. Create a BDC Application Definition. Make sure everything works fine
there.
2. Add a Business Data column to a document library that will pull from the
BDC.
3. Create a new document from that document library and ensure that the
Document Information Panel is displayed.
4. The BDC column you created in step 2 should be visible in the Document
Information Panel.
5. When you enter the primary key in the BDC column field and try to
validate this, it gives a JavaScript error saying an Object is required or
that EOF was expected and it found ":". This error is being produced from
the embedded script.js that is part of the InfoPath form. When etiher of
these errors happen, if you have Visual Studio 2005 installed, you say you
would like to debug the error and see what was going on before the error
happened.
After searching several newsgroups and finding lots of instances of this
issue but no answer, I thought I would try to post my issue here in hopes of
solving this. Not just for me but for the dozen or so other people having
this issue.
Any help on this will be appreciated by me and many other users.
Shane
Word Version: 2007
InfoPath Version: 2007
This seems to be an issue for alot of people. Basically what happens is:
1. Create a BDC Application Definition. Make sure everything works fine
there.
2. Add a Business Data column to a document library that will pull from the
BDC.
3. Create a new document from that document library and ensure that the
Document Information Panel is displayed.
4. The BDC column you created in step 2 should be visible in the Document
Information Panel.
5. When you enter the primary key in the BDC column field and try to
validate this, it gives a JavaScript error saying an Object is required or
that EOF was expected and it found ":". This error is being produced from
the embedded script.js that is part of the InfoPath form. When etiher of
these errors happen, if you have Visual Studio 2005 installed, you say you
would like to debug the error and see what was going on before the error
happened.
After searching several newsgroups and finding lots of instances of this
issue but no answer, I thought I would try to post my issue here in hopes of
solving this. Not just for me but for the dozen or so other people having
this issue.
Any help on this will be appreciated by me and many other users.
Shane