Hi Dennis, we have added some data that was missing in the oData set at the end of last year (Portfolio/KPI data and timereports) and we also have in our plan to add custom fields to the oData set. As I mentioned in my previous comment, we are aware of that the data set is not very user friendly, with a lot of information that is empty since it is using an older version of the api that in some cases pulls tables that are no longer in use. This is what we are planning to clean up in 2018.

I am however curious because you mention card comments, which is not something I was planning to include in the updates of the oData set since it in my mind is not something you would include in reporting. Could you help me to understand why you would like to have it included in the oData set?

Comments (6)

Hi Dennis!
Thanks for sharing your feedback! I will have to ask our product management team for their input. We will get back to you as soon as we can with more information.

Best regards
Silvija

Dennis Lindqvist
Dennis Lindqvist

Dennis Lindqvist

Level
0
Score
4

In the mean time, please add some of the most critical fields/tables, please.

Such as in Cardlets, connected Planlets field is missing.
And the CardConversations table is completely empty.

Hi Dennis, we have added some data that was missing in the oData set at the end of last year (Portfolio/KPI data and timereports) and we also have in our plan to add custom fields to the oData set. As I mentioned in my previous comment, we are aware of that the data set is not very user friendly, with a lot of information that is empty since it is using an older version of the api that in some cases pulls tables that are no longer in use. This is what we are planning to clean up in 2018.

I am however curious because you mention card comments, which is not something I was planning to include in the updates of the oData set since it in my mind is not something you would include in reporting. Could you help me to understand why you would like to have it included in the oData set?

Dennis Lindqvist
Dennis Lindqvist

Dennis Lindqvist

Level
0
Score
4

My idea with pulling card comments is to tag some important info that I would like to aggregate to reports.

Then the users can continue working with cards as usual. And when they wan't to high light something that should *also* be available in a report, a tag used in the text can be used to filter out that section.

I.e
WeeklyReport:The issue with (some part) needs to be escalated//

PowerQuery can easily extract what's in the tag "WeeklyReport://"

Right now, only the description field is available for such types of tagging, but that means that the description would get messy pretty fast :/

Leila Rosenstrale
Leila Rosenstrale

Leila Rosenstrale

Level
0
Score
0
Team

With the case you describe, maybe it would be even better to create a custom field Yes/no dropdown field that you label e.g. Weekly report that you mark as yes when you want to include it in the powerbi report? Given that we also provide the custom fields data in the oData set you would then have the information there and would not have to filter it our from all the other conversations. What do you think?

Dennis Lindqvist
Dennis Lindqvist

Dennis Lindqvist

Level
0
Score
4

Yes, that might be an option.
Except that I'm not an Administrator and would have to justify why all cards in the project would need this custom field that is only needed by me for my own boards :/

DIMELO - SocialCRM software editor