I have a requirement to create Web Add-in for Power Point that will change both document content and meta data. Let's call these changes templates.
The Add-in task pane will contain a drop down list for all possible templates.
When the user choose one of them and click apply button, selected template will be applied.
Each template has to add a header, a footer and custom properties to the document.
As Office.js API is not supporting custom properties manipulation, I'm thinking about defining all templates, as PPT documents with proper headers, footers and custom properties, manually. When a user decides to apply a specific template, I will copy the content of the current PPT document to selected template (existing PPT document) and continue working on the template behind the scenes.
Giving this scenario, is it possible to:
Have some predefined PPT documents as templates in an Office Web Add-in
Copy the content of PPT document to a another one and continue working on the second?
good question.. here is some guidance for you:
Unfortunately, this is not possible to implement as a Web Add-In in PPT today.
The PPT JS API is still not as rich as in Word or Excel.
I recommend you to create a VSTO Add-In for this scenario.
Please add this request to our user voice channel.
Thanks!
Related
I'm trying to recreate this functionality in a SharePoint add-in using Visual Studio 2015. I'm stuck at customizing the MS Word template to include metadata fields (DevNumber, DevOpen, etc). If I create a content type in SharePoint itself, I get a template that includes my fields as custom proprieties. How can I get similar functionality in a SharePoint add-in?
Run the app, then create a document using the default template.dotx. Update the document how you want the template to look, including adding property fields, then save the file as template.dotx in the appropriate folder - something like: https://myAppWeb/MyProjects/Lists/MyList/Forms
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.
I have been experimenting with excel online shared link to be able to embed an excel document to our internal web site. But this method is not viable because we can't actually make a public link because the data is private.
I was wondering if it was possible to embed an excel document any other way. I can add that we need an excel document with an add-in attached to it. I might have done something wrong but in my test, my add-in didn't show up in the embedded version of the document. I also noted that functionality seemed greatly reduced. Even with read-write permissions, I could input some data but couldn't delete anything which wasn't very useful in our case.
Ref:https://support.office.com/en-US/article/Share-it-Embed-an-Excel-workbook-on-your-web-page-or-blog-from-OneDrive-804e1845-5662-487e-9b38-f96307144081
Our goal is to be able to :
embed excel document into an application.
feed external data into the excel document when opened or on user input (done by an add-in)
user interaction (read-write-delete according to defined locks and column visibility)
save the relevant data to storage (done by an add-in)
save the document to OneDrive and/or to a specific location.
I am wondering if there is any solutions (now or in-progress) that would allow us to have most of the functionality of excel online while being managed by an application.
Possible solutions?:
We might have a partial solution where instead of creating a shared link, we could integrate our application to excel instead of doing thing the other way around. But it doesn't solve how to handle Microsoft accounts required to access the documents.
You'd have to do the heavy lifting in JavaScript I'm afraid and add-ins are out of the question. See a very rudimentary example of how to interact with an embedded Excel file here:
http://www.jkp-ads.com/Articles/embeddedexcel00.asp
I'm using MOSS (SharePoint 2007) and InfoPath 2007.
I have a Form Library with an attached InfoPath form, and would like to create new items (forms) in this library during a workflow built in SharePoint designer.
I've tried using the "Create List Item" action, but it doesn't assign the correct metadata (the new item looks fine in a view of the list, but can't be used to render the form (the generic "form has been closed" error comes up if you try to view the item)).
I'm not adverse to writing my own custom WFA to do this in .NET if need be, although it'd be nice to find a simpler solution.
Can anyone provide any resources for how to achieve this in SPD, or programmatically? My searches on the topic so far have been unfruitful...
Found the solution to this, thanks to a video on YouTube: http://www.youtube.com/v/bcnC_XwCcAg&hl=en&fs=1&rel=0
For anyone else out there who (like me) might not be able to watch YouTube content where they need this information, here's the process:
Create IP form
Publish to SP Server (as doc lib)
On document library, change settings:
allow management of content types
display in browser
"Fill out" a blank version of the form and save it to the doc lib with name "template"
Open context menu for "template" form and select Download a Copy
Delete "template" form from document library
Open library in windows explorer
Open Forms dir
Paste downloaded copy of "template" form into the Forms dir (as template.xml)
Go back into doc lib settings
turn off management of content types
change template url to template.xml
press OK to save changes
Go back into advanced settings ago, and turn management of content types back on
In SPD, make a WF which uses Create List Item to put an item in that library
And that's it. Just 12 steps needed to publish an InfoPath form so that it behaves as you'd expect, and any SharePoint developer should be familiar with 12-step programs.
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.