I need help to find solution to export "Word Document" with templete
that contain primary entity parameters and linked entities parameters.
I use with mail merge , but the method is carried out by a large number of operations to layout.
In CRM 2011 need to click 1 button and the Word Document is ready with all parameters.
someone can help me find solution for this situation
I can think of two options:
use a third party software like document core pack.
document core pack
develop your own plugin to create a document and dump it in a shared drive.
I have done this before with the use of openxml (you do not have to install office on the server).
openxml
Related
I have a lightswitch project in visual studio 2013, using vb.net. I would like the user to be able to click a button and have lightswitch find an excel file, and upload that file to a sql table according to a pre-determined column mapping.
My preference was to use the Office Integration extension for visual studio, which I got working with VS 2013 by downloading it from this link: http://www.ge.tt/71iuRQv/v/0
However, the documentation and examples for office integration seem to be very heavy on getting an excel spreadsheet into a display in the lightswitch web client, rather than into the sql data table, which is where I need it. Here are the examples I've been following:
http://blogs.msdn.com/b/bethmassi/archive/2012/07/18/new-and-improved-office-integration-pack-extension-for-lightswitch.aspx
Alternatively, I have an existing stored procedure, and I can request that the server call this stored proc by sending a web API extension from the client to the server. I have this working already for other stored procs, according to examples from Beth Masi and Paul van Bladel. (Stackoverflow won't let me post the links...)
The undesirable part of this approach is that the stored proc is old, and messy.
I've searched and searched, but have yet to find anyone approach this problem for VS 2013 with lightswitch. Any useful advice?
I've used the method detailed by Matt Sampson to store word files and it works very well. Since it just stores the raw binary it should handle Excel files just as well.
If you're creating the table in LightSwitch, use the Binary Type. If you use SQL create scripts use varbinary(MAX).
You need to create a custom Silverlight dialog box to gain access to the OpenFileDialog object. Then open the file in as a FileStream.
Finally, you need to add a handler for the closed method of the control and then show the control to the user. Most likely done in a button. This needs to be done on the main dispatcher.
The code examples are in C# but I just used one of the many available translators out on the web and copy/pasted the VB.NET code.
Another option might be to consider shelling out to the DTSEXEC run-time to execute an SSIS package to perform the upload - especially if the target Excel spreadsheets have predefined layouts and content data types.
Even simpler, you might be able to use the SQL Server BULK INSERT command to get the job done - although that would require a SQL Client connection to your database.
HTH
Hope this is not a strange question.
Can you attach files to a document item in a document library as you can in a list.
Short answer is no.
With SharePoint 2010, you might want to investigate the use of Document Sets which, without knowing what you're trying to do, could be a way to resolve a need for keeping grouped documents together.
OOTB SharePoint does not support attachments with Document Library.
You should create custom field type or find some commercial add-ons like Sparqube Document Column. You can add the Sparqube Document field type to any SharePoint list including Document Library and attach different files within a document item.
I'm working with Visual Studio 2010 and Sharepoint 2010. I would like to know if there's a way to have a web part that crawls all the data within a SharePoint site so I can save it into a custom db.
You can certainly create a custom web part that will do this. I do not know of an out of the box web part that will work. I began writing something like this when I found SharePoint List Source and Destination. It's a CodePlex project for an SSIS SharePoint adapter. We did not need a user interface for the extract, so we used it successfully last year for transferring data between SQL Server and SharePoint.
Sounds like all you need to do is use the API, OOB web services, or the Client OM to write some code and access the lists directly. Which approach you take depends mostly on where the code will run.
Well I found this article - Document Library Tree View Web Part for SharePoint - it is a Web Part that shows all the info of any of the document libraries within a site. At least I know how to crawl that kind of library.
We have a document library that is built inhouse. We are migrating to SharePoint 2010 Document Library, but this will be a time consuming process and many very old documents may not get moved to SharePoint at all. I would like to provide the same experience for our users when they open a document from SharePoint or our legacy system. The behavior I would like is like when you open a Workbook or Document that is rendered in the browser using the "Open In Excel" and "Open in Word" button that you get when you open a document stored in a Share Point Document Library.
I am not sure what this technology is called or where to start looking to configure this or integrate into an addin.
Any starting points are much appreciated.
I'm not exactly clear on what your question is, but perhaps you are looking to use the Office Web Apps. This allows you to use the Office applications within the browser.
I want to create a program that could generate reports from an ms access database and place it on ms word, how can I do that. Please help, I dont have any idea on how to do this.
If you're doing this from vb.net, it seems to me that it would be simpler to automate Word, which has no difficulty utilizing Jet/ACE data as data source. I don't see any reason to involve the Access application in this, unless you have complex logic that needs to be executed within Access to get correct results in Word. For instance, Word doesn't do parent/child data display very well, but Access reports do that very easily.
Another question is the final disposition of the results. It may be that you don't need Word at all, e.g., if you're using Word for nothing more than generating PDFs. In that case, it might make more sense to create Access reports and output those to PDF (there's an add-in available for for A2007, and in previous versions, you can use the VB automatable PDFCreator, which is free).
In short, my conclusions would be:
if you're just merging data in Word from a Jet/ACE data store, then automate Word.
if you need to execute complex logic, it's probably better to automate Access and either output Access reports directly, or automate Word from Access.
In neither case, I believe, would you be automating both Word and Access directly from your VB.NET application.
You should connect to the Access Database using a Typed Dataset.
Right-click the project, click Add New Item, select Typed Dataset, and follow the wizard.
To control Word, add a reference to Microsoft.Office.Word and use the Application class.
You can build reports in MS Access that have the Export to Word functionality built into them.
You can invoke the report from your code and then call the export functionality and give it parameters so that it will export to a .doc file that you name. You can then invoke MS Word and open the .doc file up for display.