ServiceMax Event Size Limit

0 Likes

We have recently discovered that it is not possible to delete WO's when the object storage limit for ServiceMax Events exceeds 200,000 records. We sometimes delete WO's for example if it is created in error or indeed the customer demand is cancelled - there is no benefit for us to keep the WO, so we delete it. When the ServiceMax Event object gets to 200,000 records there is a WOR1_Trigger error. It would be beneficial if there was a way which this can be handled better - either by increasing size storage, or by auto removing after a period of time - having to using Dataloader to remove older events so we can delete unwanted WO's is not ideal. Also, there is no notification of nearing the limitation or indeed exceeding the limit. 

What is the underlying problem do you intend to solve with this idea?
ServiceMax Event periodic deletions
How is the problem being addressed today, if at all?
Deleting old Events, and keeping size limit below 200,000 records
Product Area?
Brower, Event Management
What version of ServiceMax are you on?
19.2
Tags (3)
5 Comments
Product Team
Product Team
Status changed to: Product Team Review
 
Product Team
Product Team

Hi Mark,

Have you already opened a case about this issue? It'd be interesting to see the logs of that trigger error.

Thanks,
Gab 

Roast Chef
Roast Chef

Hi @gabriele_bodda yes - already logged on case #84441

Product Team
Product Team
Status changed to: On The Roadmap

Hi Mark,

The engineering team is aware of this issue and are looking to make the query in question selective to address it comprehensively as part of our product. The tentative plan is to try and include the enhancement in release 20.2.

Thanks,
Gab

Roast Chef
Roast Chef

@gabriele_bodda great thank you for the update!