OData Links from Self-service Portlets on PPM v24.3

Hi Team,

We're seeing the ff error below when attempting to refresh an Excel sheet pulling data from an OData source from PPM.

This was working prior to v24.3 upgrade.

From what I can see, the underlying datasource is fine and can return data when ran directly against the database. The self-service portlet is populating correctly as well.

From the logs, we're seeing a lot of entries similar to the following.

ERROR JSESSIONID=9A2D18A0C77DE4BB30223E359367E576.prod_5,USERNAME=:http-nio-8084-exec-52:(SQLDatasourceODataService.java:368):2024/09/12-12:03:26.032 SAST: Error when parsing a Number field from SQL Datasource to OData number, for value:ZAR1,000
ERROR JSESSIONID=9A2D18A0C77DE4BB30223E359367E576.prod_5,USERNAME=:http-nio-8084-exec-52:(SQLDatasourceODataService.java:368):2024/09/12-12:03:26.033 SAST: Error when parsing a Number field from SQL Datasource to OData number, for value:ZAR0

On the datasource, all the relevant fields have the column type = 'Text' so it shouldn't be converting into a number.

Any guidance would be appreciated.

Tags:

  • Verified Answer

    +1  

    Hi Harvin,

    Are you sure that you look at the right datasource information here? From the code, this error will only fire if you defined the column as a "Currency" column in the Datasource definition. 

    This OData Link might still refer to a SQL datasource where these columns would be defined as a "currency". 

    If the self-service portlet works fine, what happens if you re-generate a new OData Link from it and use it in your Excel Spreadsheet?

    In any case, this is not a known issue as far as I can tell, so I'd advise to open a support ticket - if you are confident that the issue only occurred after the upgrade and that no change was done to the datasource definition, it definitely is worth a deeper look by support/R&D.

  • 0 in reply to   

    Hi Etienne,

    The datasource mostly has column type = Text, including all of the columns that return currency values. I've regenerated the OData Link but same result. We can confirm that these were definitely working pre-upgrade and have not been changed.

    Thanks for the feedback - I'll raise this to support.

  • 0 in reply to   

    Hi Etienne,

    I've raised this with support and was provided a hotfix (ref. 02962292).

    We can confirm that the hotfix worked and the ODLinks work now for all our environments.

    Regards,

    Harvin