CiviCRM Community Forums (archive)

Hello everybody.

here is the bug I noticed :

frequency : always
context : say you have a case type with 2 activities inside (A and B)
And say A as custom fields that B doesn't have.
Then when trying to export cases, and selecting this custom fields to be exported, the export is all wrong (duplicates rows, custom fields content duplicated sometime)

Note : when exporting activitiesfrom the activity search, no problem (but we can't know the name of the related case )

Anybody encountered this bug/Knows how to deal with it?
I guess it is related to some sql querry (like a wrong Join, external where it should be internal)
It is really anoying

Rémi

no revision at all except for one
my export file is about 350 rows for less than 10 activities
 

the export action you find in the find a case page =)
The bug appends on the demo site (try to export cases with the settings ''testBugExport'' )
( 1000+ rows for about 10 cases )

I was just trying to export all the activities related to case, and some custom fields for activities witch have custom fields.
That is I want :
all cases related to a defined contact type
all activities related to these cases
when its available, the value of custom fields of activities.

The results would be a row for each activity , and details about case, contact, custom field in column (blanck or filled )


It seems really straight forward to me. Just a big export.

Rémi  

The export is obviously wrong as it indicates that some activities have custom fields value they don't have at all. (so clearly this is a bug, as the export return things that don't exist in DB)

Beside, in my opinion, what is the use of being able to select activity custom fields in export if this is bogus.

So I'll recommend to either take the activity custom fields out of the export list, or fix this (again, probably change the join type).

I'm currently using OO Base to execute query in a graphical way, and I was looking for another solution has it is really painful and nearly impossible to maintain over time. ( In the end its like remapping every relations between civicrm tables, and this work as already been done by the mighty developers. )

So if anybody just need a raw list of activities in for-export-selected-cases with their custom field, I'll recommend NOT to use any SQL querry, neither use macro, but instead to use civicrm export function to custom tailor it (this should win you several time !) (thinking about the DAO stuff)

Rémi