More export options for usage logs

Hi Niklas,

Could you tell us more on your need, particularly, why you would like to specify which columns to export ? Is it to feed another system that is not able to filter out some fields ? And is it only for that report or it is something that could be useful for other reports as well ?

It is something that we could add as option for sure, but I just want to be sure that we will build a solution that will cover all your needs.

Best regards,

Hi François,

The reason for the additional fields is the desire that we can compare the activity in RDM with the reported hours on the customers. We would like to achieve more transparency here and therefore need certain fields.
Currently, we are working with a workaround in which we map the CRM ID in the customer name (e.g. "4711_Customername", extract this "4711") and make the link to the reports.

Greetings
Niklas

Hi Niklas,

Thank you for your reply. I think I misunderstood. I thought you wanted to be able to select which fields you wanted to export, but now, what I understand is that you would like to add more field in the report, am I understanding correctly ? If it is the case, what information you would like to add ?

Best regards,

Good day

Sorry, I also expressed myself incorrectly. The idea would be to assign a value to the top object, which is automatically passed on to all other objects below it. So that we can assign an ID, and then have this ID in every event within this folder in the log. Currently, we have to use queries to get this ID out of the directory path, which does not always work properly. There are already tags, but these would have to be inheritable and displayed in the log.
But more important would be the export as ".tsv" file.

Kind regards
Niklas

Hello Niklas,

Thank you for your reply, now I understand your goal. I will create 2 different feature request tickets on our side. One for the "tsv" format and one for the additionnal information that could be added in the report. The first one should not be a problem, the second one will require discussions internally. We will post here as soon as we make progress on those requests.

Best regards,

Good day together

Has something come up here, unfortunately I haven't heard anything so far?

Best regards
Niklas

Hello Niklas,

We don't have an ETA for that. I will see if we could try to do the tsv file since I think it is what it is important for you. The second request is not currently planned. We took note of your feedback and will follow the topic to see if there's any additional interest or input from other users.

Best regards,

Hi have the original question as NRATHMER above. But my need are litlle bit different.
The subject remain the same " More export options for usage logs "

My justification is more like.

A) Be able to select ourself the delemiter [ most common would the TAB Delimiter] and avoid the field "Comment" with comma, to come and "BREAK" the import into another system , for incorrect data format. in that case accepting tab or comma or semicolon as delimiter, Developpers then also need to avoid end user to user those character and any fileds that would come into play at the export process.

B) Be able to add or remove columns as per need.

I hope this could be more considered as a valuable feature request enanchment.
Best regard's

Hello,

Thank you for your suggestion. When there is a comma in a value, it usually is not a problem if the string is enclosed in quotes ("xyz, abc"). Do you have an example where it creates an issue? However, I understand that it could be useful to export with a different delimiter, but the issue persists if you use a semicolon (;) and have it in a string. If that string is not enclosed in quotes, it will be a problem. I just tested, and we export it enclosed in quotes when required, so it should not be a problem. Please let me know what version you are using; I could double-check if there might be an issue.

However, I keep in mind that having different delimiters and the ability to select the columns you need could be useful. Is it because you would like more information in the report, or just because you want to remove data that you don't need anyway?

Best regards,