SharePoint Reports and Documents Generator 2.0 released

image We are happy to announce, that new version of SharePoint Reports and Documents Generator just released. Due to the fact that Microsoft had to remove custom XML feature from MS Word, we have decided to release a new major version of SharePoint Reports and Documents Generator. In the new version we have changed the way the new templates are created. We hope those changes will increase usability.

Here is the list of other introduced features:

  • Sharepoint Server 2010 and SharePoint Foundation 2010 support added
  • MS Word 2007 and 2010 (32 and 64 bit) are supported
  • Possibility to apply style on inserted field data
  • Rich text fields are now supported  (commercial version only)

As always you can download and try free version. To find differences between free and standard version of Generator click here.

We are looking forward  for your feedback!

Posted in Sharepoint Report Generator
31 comments on “SharePoint Reports and Documents Generator 2.0 released
  1. Randy says:

    I just purchased v1.1 a couple of months ago. Is there a way to upgrade?

  2. sigitas says:

    Yes, of course. Our original policy was to provide free upgrades only for minor version changes during support period, however due to MS XML issue this time we decided to provide major release update for free for users which support period have not been ended yet. At the moment we are solving some technical issues. Expect an email within several days.

  3. Peter says:


    I’m trying out your product, but I cannot get it to work. Using the MS SharePoint 2010 vhd.
    My fields that are lookups dont work. Also the document wants to save locally instead of in SharePoint. What am i doing wrong?

    • sigitas says:

      Hi Peter,

      to save document to the document library custom action parameter &returnFile=Yes should be removed or set to &returnFile=No .

      It’s hard to say what are you doing wrong without seeing what you are doing 🙂 At the moment I just can tell to double check if there are no mistypes. Also Field tag attribute name shows to the field in the “current” list and lookupListField is the name of the field in other (lookup) list.
      If you still will be unable to solve issues – send description of your lists (maybe screenshot of fields) and document template to

  4. Randy says:

    Do you know of any issues with the formatting of content controls? I have created a template which uses tables for positioning and alignment. If I format the cell it loses the format upon opening the document. If I apply a style to the content control through properties, it to loses the formatting. Am I missing something?

    • sigitas says:

      Actually, (if look to the docx internals) there are several ways to format text – text itself, cell and content control properties. We have decided to prefer content control properties. However, I think, the best way to comment this issue would be if you could send us template (and, if possible, result document). Then we could investigate exact problem and tell you if this is issue or feature and maybe we will be able to suggest some workaround if necessary.

      • Randy says:

        I have been working with the assumption that formatting was acheived through the content control property and the use of styles.

        It appears that the document reverts back to the “Normal” style regardless of the style used in the content control. I confirmed this by modifying the formatting of the Normal style which was retained when the document opened.

        In addition if I modify the template outside of the sharepoint environment (i.e. saving it to my desktop and using the template to create a document)the formatting is retained.

        Where should I send the template and document?

  5. Thomas Stessl says:

    Not working:

    System.ArgumentNullException: Key cannot be null.
    Parameter name: key
    at System.Collections.Hashtable.get_Item(Object key)
    at Microsoft.SharePoint.SPFieldCollection.GetFieldByInternalName(String strName, Boolean bThrowException)
    at Microsoft.SharePoint.SPFieldCollection.GetField(String strName, Boolean bThrowException)
    at Microsoft.SharePoint.SPFieldCollection.GetField(String strName)
    at Microsoft.SharePoint.SPListItem.GetFormattedValue(String fieldName)
    at Novitas.DocumentGenerator.DocumentGeneratorPage.OnLoad(EventArgs e)

  6. Andreas Nahr says:

    This is a GREAT product!!
    It is a bit tricky to use, but version 2 is much easier.
    I do have one issue:

    The times in the SharePoint list are 6 hours off the times in the resulting Word document. I am in the Central US time zone.
    in the SharePoint form, a deadline is set at:
    1/13/2011 3:00 PM

    The Word document displays the deadline time as:
    1/13/2011 9:00 AM

    Sharepoint is WSS 3.0 on a Windows Server 2008 R2 64-bit
    Client is 32-bit Office 2010 on Windows 7 Professional 32-bit

  7. sigitas says:

    Thanks for your feedback. We will investigate this problem. It looks like this could be time zone issue. Meanwhile as workaround you could create some calculated column with deadline -6 hours and use it value when document is generated

    • Andreas Nahr says:

      Thanks for the tip… it worked great!
      I addded 6 hours; the Formula is “=Created+0.25” (the 0.25 is 1 day divded by 24 (to get hours) multiplied by 6; 0.25 = 1/24*6)

  8. Randy says:


    I know I’m missing the obvious but when I try to create the custom action button on my dispform I get the following error.

    System.ArgumentException: Value does not fall within the expected range.
    at Microsoft.SharePoint.SPListCollection.GetListByName(String strListName, Boolean bThrowException)
    at Microsoft.SharePoint.SPListCollection.get_Item(String strListName)
    at Novitas.DocumentGenerator.DocumentGeneratorPage.OnLoad(EventArgs e)

    while using the following URL

    Url=”~site/_layouts/generate.aspx?docLib=RMA Acknowledgments;conType=Print RMA Acknowledgement;docName=RMA-;returnFile=Yes;suffix=ID;listName={+ctx.listName+};itemID={+currentItemID}”

    What’s funny is I have the following URL in a CEWP and it works fine but it doesn’t work in my feature. I had to replace the “&” with “;”.

    url = ctx.HttpRoot + “/_layouts/generate.aspx?docLib=RMA Acknowledgements&conType=Print RMA Acknowledgement&docName=RMA-&returnFile=No&suffix=ID&listName=”+ctx.listName+”&itemID=”+currentItemID

    Any suggestions?


    • sigitas says:


      “&” replacing by “;” does not look valid (maybe it should be replaced by “&” ?)

  9. Randy says:

    You are correct. I just tried the & and it looks better but it still is not working. I think it is the listName and itemID paramter.

    In a custom action on the display form should it read listName={ListID}&itemID={ItemID}



    Should the parameters be in brackets?

    • sigitas says:

      When you create URL you must provide listName and itemID. In custom action placeholders with brackets are automatically replaced by SharePoint itself. In other places (like dispform) you need to find values yoursef. E.g ID could be find from query string and list name hardcoded – depends, what way way do you use to add that button

      • Randy says:

        Gotcha. So I can hardcode the listID and then use the itemID from the query string.

        For example itemID={@ID}?

      • Randy says:

        I created a custom action through a feature based on the example from the user guide.

      • Randy says:

        Url=”~site/_layouts/generate.aspx?docLib=RMA Acknowledgments&conType=Print RMA Acknowledgement&docName=RMA-&returnFile=No&suffix=ID&listName={65A209BA-56FC-4B77-BAA0-BDCFD32AC166}&itemID={@ID}”

      • Randy says:

        System.ArgumentException: Value does not fall within the expected range.
        at Microsoft.SharePoint.SPListCollection.GetListByName(String strListName, Boolean bThrowException)
        at Microsoft.SharePoint.SPListCollection.get_Item(String strListName)
        at Novitas.DocumentGenerator.DocumentGeneratorPage.OnLoad(EventArgs e)

      • Randy says:

        In my dispform query string I have the following values


  10. Randy says:

    Sorry I meant the “&”

  11. Randy says:


  12. Randy says:

    Turns out the URL is exremely case sensitive. I had

    listName={ListID} and it should have been listName={ListId}

    itemID={ItemID} and it should have been itemID={ItemId}

    At least that’s my theory. Thank you for your help.

  13. Habib says:

    HI guys

    I am using document & report generator 2.0, everything is looks fine but the generated document is not showing field data. I am trying to print a field ‘title’ only.

    I will appreciate your response

  14. tr?n c?c says:

    I installed d&r g with office 2010 but task pane enable and i cant access it. Please help me!

  15. Bob Endress says:

    Are you still selling your product? I am interested.