File Corrupt Issue and Download Option - .xlsx

Answered

Comments

7 comments

  • Best answer
    Avatar
    Ben Bauer

    Hi Vamshi,

    You are welcome to open a Support ticket for some more detailed assistance on developing a custom webapp page that can download true XLSX files.

    Here are general options I can recommend:

    • Use Excel Integration - I know you specifically want to avoid this option, but it is our most actively developed Excel feature in the toolset.  SST/DSP releases often include enhancements and fixes for this feature.  On the other hand, the page Download option has not been updated for quite a few years.
    • Add a button to the custom page toolbar that links the user to a dspMonitor/dspMigrate report page where the file can be downloaded.
    • Add a button to the custom page that executes an Assemble package to generate the XLSX file.  Add another button that allows the user to download the generated XLSX file.
    Comment actions Permalink
  • Avatar
    Joseph Flesche

    Question 1:

    The file that is downloaded is not truly an Excel file. It is HTML / XML (I forget which one it is). If you open the file in notepad (or some equivalent program) you will see the file content.

    To get rid of this message, you would need to change security settings in Excel.

    Question 2:

    Unfortunately, I am not too sure of any additional options here.

    0
    Comment actions Permalink
  • Avatar
    Vamshi Krishna Akinapally

    Hi Joseph,

    Thank you for your response.

    Question 1: In our project more than 50 Users are facing this Issue and Changing Security Settings for Indiviual users in not Possible :(.

    Can you please let me know If there is anyother way to get rid of this Message.

    Question 2:

    If Client Wants to download it in Excel format. How Should I proceed Further to include this Additional Option in Our tool.

    Regards,

    Vamshi

    0
    Comment actions Permalink
  • Avatar
    Joseph Flesche

    Vamshi Krishna Akinapally,

    Question 1: If I register a report within dspMigrate and then download the report, the file downloaded is a true xlsx file and I do not get the warning message. Another way that I was able to get around this (when we worked in Cransoft, I have not implemented this in DSP), was to run a VBA script to loop through all of the "xls" files, open them and then convert them to xlsx, save, then delete the "xls" file. After this is done, you need to tell DSP the new file name.

    Question 2: I forgot about the report option. I would suggest that you try that through dspMigrate (or some other WebApp within DSP).

    0
    Comment actions Permalink
  • Avatar
    Vamshi Krishna Akinapally

    Hi Joseph,

    Question 1: Actually User want to download the data which is present on Custom Webapp. 

    Question 2 : I want to include that Option in Custom Webapp page.

    Regards,

    Vamshi

    0
    Comment actions Permalink
  • Avatar
    Joseph Flesche

    Ben Bauer,

    For option 3, do you have any links / instructions on doing this? I can see how this can assist with end user interfaces on our end.

    0
    Comment actions Permalink
  • Avatar
    Ben Bauer

    Hi Joe,

    I prefer to use a Support ticket for specific questions about that 3rd option, but I can give a bit more of an overview here.  We don't have any article detailing it (yet).

    That 3rd option works best on a page that will not be filtered by the users.  While the button executing the Assemble package could certainly take into account the binding/drilldown criteria of the page, it can't take into account any text/column filtering that the user has applied to the page.  It also works best if an Assemble package can be generated including the boaUserID (to prevent simultaneous user actions from deadlocking or conflicting in some way).

    The button that executes the Assemble package can do this by running a stored proc that utilizes the CranSoft.dbo.boaJobAddCranPortTask proc.  Example:

    If you will be creating the Assemble package within the proc so that it includes boaUserID and/or the page's binding/drilldown criteria, then you can use the CranPort.dbo.boaCreateCranPortPackage proc.  I recommend making one package manually in Assemble's frontend first, and then reviewing the values in the backend CranPort.dbo.CPPackage table.  This will show you what sort of values you want to use in the parameters for the CranPort.dbo.boaCreateCranPortPackage proc.

    The button that allows the user to download the file should link to another page (vertical-only if you want it to appear as a popup) that has a standard File column property (Help link) for downloading the XLSX generated by the Assemble package.  If you are having 1 Assemble package per user, then the table underlying this page will need to include boaUserID.

    Again, this is not a simple option, so there are bound to be several specific questions that are best handled in a Support ticket.

    0
    Comment actions Permalink

Please sign in to leave a comment.