HI Bjørn,

I created an installed item not linked to a contract on our standard current version having a PM Commencement Date and PM Schedule linked to the item.  This is picking up the PM Dates properly in the Web Employee Portal - PM Batch Scheduler.

PM Dates are defined against the installed item:

As the Astea Browser does find the dates for you, this is likely to be a data issue that causes a problem with the web employee portal.

Please log a support case for this issue with the details so we can check this with a copy of your database with the appropriate DB profile.

Also double-check your item has the proper definitions defined for the PM’s.  Example below:

Hi Bjørn,

I think this is an issue with the Web Employee Portal code as I just reproduced this while using a specific serial number which has a PM Date next month. 

The PM Batch Scheduler does find the serial number in the search if you do not specify the Node ID but once you do specify the Node ID, the search returns nothing.  All criteria are the same only changing the node id.

Without Node ID

With Node ID

It may have been fixed in a later version (which I am checking now) as it did not reproduce the issue in standard.

Thanks, Phil - let me know how it goes

Still want me to log a ticket?

Please log the support case… we need to narrow down where this differs with your data and the code.  The basic premise of an item not being on a contract has proven to not be correct as the root cause.