We're implementing SharePoint 2007 but have Office 2003 as our client. This causes problems when editing metadata since custom field types like BDC columns aren't represented properly within the Web File Properties dialog in Word. To get around this, we would like to disable the this dialog to force users to edit metadata within SharePoint.
How can we do this? Also, are there other alternatives that we should consider (short of upgrading to Office 2007)?
We use a product called metaEngine to customize the Office properties dialog. (I have no affiliation with the company)
Essentially it uses an httpModule to detect when the Office properties dialog is called and injects / rewrites the html to provide a custom editor for metadata. You could either use this approach, or use a similar httpModule to present a "this functionality is disabled" type screen.
Have a look at the requests going between Office and SharePoint using Fiddler and it'll give you an idea of what you could change.
Related
Our Web Application stores/creates documents for clients. Our clients download these document which contain custom tagging parts which are client specific and stored the customxml part in both Excel and Word documents. We currently use an activex ribbon bar app that retrieves these parts and displays them for the user. This allows them to access these parts to be inserted into the document by the ribbon bar app.
We then sought a better and more compatible way to accomplish this to get away from activex but also allowing clients that use older version of Word and Excel to continue to use the activex control.
Microsoft assisted us in creating our Word Addin that used Angular and Office js to accomplish this in MS Word.
Now we need to replace our Excel ribbon bar app. I am leading the creation of this tool and found that Excel API currently does not allow access CustomXml Part in the document structure.
Is there any way to access the customxml part in Excel?
Is there any plans to allow access in a future release.
Can you recommend a best practice for storing and retrieving these part if the first two question are no.
We are using Angular2 and Office.js to create the new addin.
I believe this is coming soon in API set 1.5 : see the open spec details here
https://github.com/OfficeDev/office-js-docs/tree/ExcelJs_OpenSpec/reference/excel
As Charles mentioned, Custom XML parts API will be available as part of Excel API #1.5 set.
If you have 1702 build of Excel, you can test this out now. See here for details.
QTP doesn't recognize item when I disable some add-ins which was checked when I added them in to the repository
Note: I actually selected all the add in's when I added the objects into repository - .Net, JAVA, Oracle, Siebel, SAP, Web Services, Silverlight, ActiveX(I know I am a Noob). When I just select Web right now and run the script, it's unable to recognize the object and when I add the object again(with only Web checked), it's being added as a new object and is being recognized when I run it.
So my question is what is the relationship of an object with respect to add in? How does it go on to affect the property of the same object?
Add-Ins are Collections of Pre-Defined Object Types
The add-in contains built-in property sets for a specific group of related UI objects. This helps QTP identify the runtime objects more effectively for a specific type of application.
For instance, it's quite predictable that browser-based applications will be using the standard HTML elements, so the basic web objects (i.e. Page, Frame, WebButton, WebList) have already been defined in advance inside the Web add-in.
The Evil in Enabling All Add-Ins
Most likely, you're facing the issue because all add-ins were enabled during recording. QTP had the option to choose from any of the pre-defined objects in all of those add-ins as it sees fit. You could have ended up with an object repository that's a hybrid of object types found in multiple add-ins.
We faced this similar issue before where a web button (i.e. html input type="button") was recorded as a SAPWebButton. That's because all add-ins were enabled during recording and no one noticed. It worked fine until we disabled all other add-ins, except for the Web add-in. Since the Web add-in only knows about a WebButton not a SAPWebButton, this resulted into identification problems.
Prevention and Fix
The correct approach is to decide which add-in is most appropriate for your application type before recording, enable it and disable the rest.
You will have to manually update the problematic object via Update Run Mode. If there's too much, you'd be better off recording from scratch.
I have a requirement to develop a custom control for use in InfoPath 2010 web browser forms, I've looked in all the usual sources (MSDN, InfoPathDevelopers Centre, SO etc.) but I haven't been able to find any reference or tutorials on how to do this.
Most of the documentation I have been able to find has been InfoPath 2007 specific and uses Active X for custom controls, a practice which is no longer supported.
In this particular case, the requirement is to add Captcha to whichever forms require it, but I'm expecting similar requests in the future.
Does anyone know of any resources for InfoPath 2010 custom control development, or even if this is supported?
Many thanks
Tim
As far as I can make out this feature is no longer supported, it was previously possible using Active X (so not usable outside of IE) but now that support has been discontinued.
I am running Sharepoint 2010 with Office Web Apps. By default, any document of type .doc, .ppt, etc... will open within the browser from the document library. This is fine, however I am using a web part that is pulling in an XML feed that displays a search engine result list that contains URL links to Word and PPT documents.
I would like to have these links behave the same way as they do in the document library (open in browser), however the user is prompted to download these files instead. Is it possible to dictate this behavior in Sharepoint?
Unfortunately I don't think this is possible unless the documents are hosted in SharePoint and the Office Web Applications feature is activated. The in-browser behaviour is made possible by this server-side feature. I assume that the search-engine derived links you are getting will not, in general, be SharePoint hosted documents.
It is possible to open documents in the browser, but this is a client setting and will depend on the client operating system. You say you want to control this from SharePoint, and I can't think of any way you can do this.
I’ve got a moss document centre website with FBA and AD authentication enabled. After creating a picture library I seem to have reduced functionality when accessing the site through the FBA URL.
I’ve compared the web.config files from each IIS website and they are the same (apart from added FBA information that's required).
Here's two pictures to illustrate what I mean.
This picture shows the options available in the picture library when accessing the website through AD authentication:
alt text http://www.abbeylegal.com/Downloads/2006-07-26/Ad%20Authentication.jpg
This picture shows the reduced options available in the picture library when accessing the website through FBA authentication:
alt text http://www.abbeylegal.com/Downloads/2006-07-26/FBA%20Authentication.jpg
Anyone else seen this behaviour? I find it really strange.
This functionality is by design. As per Microsoft:
When you configure a zone to use forms authentication, the Enable Client Integration box is cleared by default. If a zone is configured in this way, the following changes occur in functionality:
Support for remote interfaces is turned off. That includes WebDAV, SOAP, and Microsoft Office FrontPage remote procedure calls (RPC). Some functionality is not available, such as Web folders or the Web services for accessing content in that site.
Some toolbar items no longer appear:
New Document
Open in Outlook
Open In Windows Explorer
Export to Spreadsheet
Open with Database Program
Explorer View option is hidden.
Create an Access View option is hidden.
In picture libraries, the following functionality is removed:
Upload Multiple
Edit Picture
Download
Send To
On the Edit Control Block (ECB) menu, the drop-down menu that appears when you click - items in document libraries, the following items are removed:
Edit in Word
Edit in Excel
Edit in PowerPoint
Discuss
Connect To Outlook
In slide libraries the following functionality is removed:
Publish Slide
Send to PowerPoint
Also, syncing SharePoint data with Microsoft Office Outlook no longer works.
Form Authentication will reduce some functionality such as in document library. We won't see the new document, be able to edit it in the spreadsheet, be able to open it with Windows Explorer etc.
For that, we need to enable the feature called Client Integration in Authentication
Provider. After enabling that, we'll get all menu items.