Error Encountered with 7pace Timetracker API Integration in Power BI accessing CustomFields

Dear 7pace Timetracker Support Team,

I hope this post finds you well. I am reaching out to request assistance with an issue I have encountered while using the 7pace Timetracker API in conjunction with Power BI.

Recently, I have been working on integrating our application with the 7pace Timetracker API to retrieve data related to time tracking. I am utilizing Power BI as a tool for data visualization and analysis for this project.

However, I have run into a problem when attempting to execute a query through the 7pace Timetracker API from Power BI. When making the query using the following URL:

https://{organization}.timehub.7pace.com/api/odata/v3.2/workItemsHierarchy?$select=CustomStringField1,CustomStringField2,CustomStringField3,CustomStringField4,CustomNumericField1,CustomNumericField2&customFields=Custom.String1,Custom.String2,Custom.String3,Custom.String4,Custom.Num1,Custom.Num2

I receive an error with the code "UnexpectedError" and the following message:
"Value cannot be null. (Parameter 'member')"

I have reviewed the documentation provided by 7pace Timetracker to ensure that I am using the API correctly, but I still encounter this issue.

Additionally, I would like to mention that I have been compelled to perform this query through HTTP instead of using OData. This is because I require more than the five custom fields allowed by the "#customFields" parameter in the OData query. I need to obtain a broader set of custom fields (6 in total like can be seen in the request above) for my analysis in Power BI.

Could you please provide any guidance or suggestions on how to resolve this issue? Is there any additional steps I should take to address this error and obtain the necessary data for my analysis in Power BI?

I greatly appreciate your time and assistance with this matter. Please let me know if you need any further information from my end to investigate this issue.

Looking forward to your prompt response.

Best regards,

Aritz Candina

Vanja Pletikosić

April 25, 2024 15:18

Hello Aritz,

Thank you for reaching out to us.
There is a limitation to being only able to fetch 5 custom fields from our API, as stated in our documentation. However, we tested it again using HTTP, as you are doing, and the limitation still remains, so it is not possible to query for more than 5 custom fields, no matter which method is used.

That being said, the system of numbering the custom fields in the select must all follow 1-5. Even when you are using different types of fields, the numbering must continue through 1-5.
In your example, you should have CustomNumericField5 in your select, instead of CustomNumericField1, and then your query will work.

Please let me know if this helps.

Best regards,
Vanja Pletikosić
Technical Support Engineer

Error Encountered with 7pace Timetracker API Integration in Power BI accessing CustomFields

Comments