Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
I use Notes 12.0.2 and Word 2021 (local install)
The Notes client still has a menu option called >Create >Word Memo.
On my machines this is useless and doesnt work properly. Assuming it is not just my installations with a problem, then if HCL doesnt want to (or can't) implement this feature then they should delete the feature. It just makes the client look like it comes from the stone age.
> May be OpenOffice, instead of MS-Office ?
OpenOffice AND MS-Office integration! :)
May be OpenOffice, instead of MS-Office ?
Import/Export to Excel is requested from all my customers. Has made my own import/export functions as Lotus Script agents (attached for free use) - but it would be a lot nicer if this was included in the product
I have a set of LotusScript libraries that enable me to use MS Word template documents where fields or text insert locations are identified using the MS-Word Bookmark function. I use a profile document to define relationships between specific Notes fields and MS Word bookmarks, and store the Word template in the profile document. My main issue is that Bookmarks in MS Word operate COMPLETELY differently if they are in document Headers and Footers! I can build a Word document, save it as a Notes attachment, print it (multiple copies can use different values in specific Bookmarks) and turn it into a PDF file very quickly, which can then also be attached tot he Notes document, ready to be mailed directly to a customer if necessary (think Estimates/Quotes, Sales Orders, Purchase Orders, etc). The Word templates can be easily modified to change their look and feel, incorporate company logos, etc, without affecting the layout of Notes forms.
The same approach can be used with Excel documents.......
Any integration help customers and enhance Notes & Domino appeal.
We, as a BP, need both effects
Agreed .... copy-as-table is heavily used, exporting to Lotus 123 is embarrassing... we've normally ended up with reporting pulled into custom Excel sheets with graphs, pivot tables or whatever needed based on some of my older Notes-excel code here: http://www.dragon-it.co.uk/link/lotusnotesutils - we've then had to combine that with data from SQL, Active directory or other systems quite easily.
Integration with MS Office requres dramatic improvements. For instance, support of MS Word Mail Merge funtion and Send To
Being able to display live Notes View data in Excel in a chart would be most useful Obviously, this would not be a problem if we had live data interchange between Notes and Excel
Edit / Copy As / Table is good, but couple of issues, a) it has a limit to number of docs in a view it will export, and b) can't point Excel to it and have a user simply refresh the data in Excel.
The ability to map an Excel table to a view in Notes would be a game changer imho. I've done this using a web callable agent that converts a view into an xml feed, but authentication is cumbersome.
The business users are all about information, and most want to be able to manipulate data in Excel. Being able to, for eg., display live Notes data in Excel pivot tables and pivot charts is very powerful and very useful.
End users may use "Edit -> Copy As -> Table" to copy data of views to Excel easily, as long as there is not to much data. Much easier than export and import.
Not being able to directly import and export to Excel is the most embarrassing part of Notes.
IMPORT into views too!!
I'd like to see the new DGQF be used to create scheduled data exports. Also, these exports should include the population of a target RDBMS such as SQL Server, Oracle, or SQLite. When using an external database, it should maintain true database currency including an accurate view of all CRUD updates. Then, the new target database can be used to pull data directly into PowerBI, Tableau, Cognos, or any reporting/query tool.