Thanks everyone for clarifying - what a pleasant surprise ^^ IMHO we could close his issue - what do you think, @jmargraf ?
Thank for the info Jon. Quite a few of our customers had the wish to be able to choose different e-mail-adresses for different bulk Mailings so we thought it may a feature that others are interested in, too.
Would be interesting what others think - if this is to specific we can of course also do an extension...
Thank you Johannes. I wanted to add that we would be able to provide (some) funding for this feature and it would be great to get a rough estimate for this.
Let us know if you have questions or would like to discuss this feature
Cheers, we will test that asap!
We (SYSTOPIA) could also pledge eight hours. We may even be able to provide a bit more but sorting this out will take some time. Will get back to you asap.
This is still an issue and can be reproduced on the drupal sandbox (currently 5.54.alpha1). Could someone take a look at it?
It seems I am not able to reproduce the error on the demo - sorry for all the fuzz :/
I guess we could close this issue unless someone else has this problem.
Sorry for the delay, after quite some digging it seems that the error occurs only if the relationshop label contains a special character. Currently the drupal sandbox has some (unrelated) issues but I will try and reproduce the error there asap.
Sorry for the delay, I tried hard to replictae & debug but so far to no avail. Unfortunately for security reasons no external people (currently not even us) can access te customers environement in which the error occurs.
I will get back asap, hopefully with more information.
Thank you for looking into this issue. Currently I cannot reproduce this behaviour on the official demo (5.47.alpha1) on October 25 2021 it was still possible (don't know the version back then).
Any idea which relevant parts of the core code may have changed since then?
Just a short update: We would be able to provide funding (currently up to three paid hours) to fix this issue.
I assigned the issue to you @monish.deb as I understood you are working on it. Would be great to get a quick update on the status here.
+1
When exporting data after an advanced search the exported file is empty if:
The export preview shows all information correctly but the exported file does not contain any data.
The export file is empty although the export's preview shows all information correctly (in case you choose data to export and not export primary fields). Note that the export will work as intended if you do not set "Display results as" to "related contacts" or do not have at least one search criterium was a custom field.
Export file should contain data of selected contacts
Possibly unrelated but referencing #2873 and assigning to @monish.deb as there is currently a fix for the export feature in progress.
@monish.deb Thanks again for looking into this. Are there any news and/or could we support you in any way?
@monish.deb Due to the time zone differences and my currently limited working hours chatting may unfortunately be a bit complicated.
However after further investigation it seems as if this is only occuring when the system's default language is not English. On the drupal master demo I could reproduce it as follows:
This still works as long as the system's default language ist English (both the main contact's and the related contact's data is exported). Switch it to another language (e.g. German) and the related contact's information wont be exported.
There were issues before in which the export relied on field lables instead of names maybe that may be worth investigating.
Thanks, let us know if should test anything.
So far we have funding for three hours. We hope to get the rest from another client but it will probably take three weeks or so to get feedback.
Thanks, I will contact our customer and get back to you asap
There is an old bug described on the old issue tracker that prevents related contact information to be exported via the UI if one of the contacts is a subtype. https://issues.civicrm.org/jira/browse/CRM-16693
If one of the contacts is a contact subtype or the relationship is defined to be only allowed among subtypes the exported columns won't contain any data (data of the "main contact" will be exported correctly).
Data of related contact should be exported as well.
We may have funding to fix this bug and would appreciate an estimate from the core team.