SAP Knowledge Base Article - Preview

3166674 - MDF Workflow Todo category related API issues

Symptom

Customer is using Todo API or TodoEntryV2 API, and the API returned data is less or more than they expected with MDF todo categories as filter (14, 17, 18, 21, 24, 25, 29, 39, 46). 

 

It is probably because the Todo category change of MDF objects.

For example:

  • /odata/v2/TodoEntryV2?$filter=categoryId eq '39' and status eq '2' and userNav/userId eq '012570' and wfRequestNav/status eq 'PENDING'
  • /odata/v2/TodoEntryV2? $filter=categoryId in '46','18','29' and status eq '3' and completedDateTime ge datetime'2021-09-13T05:37' and completedDateTime le datetime'2021-10-13T05:37' and createdDate ge datetime'2020-12-31T16:00' and createdDate le datetime'2021-01-01T15:59'


Read more...

Environment

  • SAP SuccessFactors HCM Suite
  • Metadata framework (MDF)

Product

SAP SuccessFactors HXM Suite 2205

Keywords

KBA , LOD-SF-MDF-OBJ , Object Definition & Field Related Issues , LOD-SF-MDF-WFL , Custom Object based Workflows , Product Enhancement

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.