Forums - Thread Details
  • State Not Answered
  • Replies 2 replies
  • Subscribers 320 subscribers
  • Views 391 views
  • Users 0 members are here
Forum Actions
Related

API call PUT to /Notifications

Jérémie Desmarais

   1Hello ! 

I'm trying to get rid of the unread notifications. I have about 2000 notifications to read, which are solved right now, so I don't need them. 

Impossible to get rid of them from the interface: cannot filter by "is read". The filter is not showing any column for this module.

Clouded solution so I can't create my own filter. 

Usualy I just do those massive updates with an api calls loop using a small C# programm:

" For all notifications ID where is_read is false {

    is_read = true;

}

It works, on the api call GET for all those notifications, all of the is_read fields all "true". But on the interface, I can see them as unread. 

Is this a known bug ?  Is there something I'm not doing right ? 

GET COUNT result for the is_read = false field:

{
    "filter":[
        {
            "is_read":"false"

        }
    ]
}
{
    "record_count": 0
}
View on the interface of all notifications - as you can see, there is still plenty of "is_read" = false: 
Thank you, hope my question is clear! 
Parents Reply
  • 0 in reply to Rodrigo Manara

    Hi Rodrigo, 

    Yes, all tested with postman, all responses are 200 OK : as well as the is_read attribute is true. 

    This is the notification on the interface:

    and this is the GET response : 

    {
        "id": "606a3cae-f67c-11ee-985e-022883841b4a",
        "date_modified": "2024-04-09T10:25:19-04:00",
        "is_read": true,
        "locked_fields": [],
        "_acl": {
            "fields": {}
        },
        "_module": "Notifications"
    }
Children
No Data