[ 
http://mifosforge.jira.com/browse/MIFOS-3800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

keithwoodlock updated MIFOS-3800:
---------------------------------

    Fix Version/s:     (was: Mifos Backlog)
                   Unscheduled

> Uploaded file reports should be given unique filename
> -----------------------------------------------------
>
>                 Key: MIFOS-3800
>                 URL: http://mifosforge.jira.com/browse/MIFOS-3800
>             Project: mifos
>          Issue Type: Improvement
>          Components: Reports Module
>    Affects Versions: Release 1.6.0
>            Reporter: Ryan Whitney
>            Assignee: mifosdeveloperqueue
>             Fix For: Unscheduled
>
>
> This is currently happening with BIRT, but once we move Pentaho in we might 
> want to address this
> REPRO:
> 1. upload a report template into mifos
> 2. upload a different report with the same filename as a different report
> EXPECTED:
> Can run both reports
> ACTUAL:
> Since the reports have the same filename, it overrides one
> This requires the MFI to know the filenames of all the underlying files.  As 
> their collection of reports grows, this could become more common, or they 
> might name a file the same name we have for one of our reports.  SEems 
> easiest solution is to take the filename and append an ID to it to keep it 
> unique.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its 
next-generation tools to help Windows* and Linux* C/C++ and Fortran 
developers boost performance applications - including clusters. 
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues

Reply via email to