Solution to issue with 'Currently clocked in' field in Operation Planning

There was an issue where the 'Currently clocked in' field in Operation Planning was not being determined correctly from another administration. This issue has now been resolved.