Handle aliases more appropriately

[Jason-Dang]

Description

Motivation and Context

Sub Panel aliases experience some weird behaviour due to bean and list view query caching.
The first value gets processed correctly, but is then cached in the BeanFactory which ultimately causes the alias to be cached by the list view query. Ultimately this leads to a check on the cache always skipping any processing for subsequent record values, resulting in the values being set straight from the DB etc. Additionally whenever the logic is fired it coverts to user date time format regardless of field type meaning aliases can only really be used on date time columns.

Changes

• Bypass cache check so aliased values always set.
• Check dbType before casting values to datetime.

How To Test This

1. On any module with an Activities Sub Panel, add a couple Task records with various due dates.
2. See that the first is processed while subsequent records are not.
3. Apply the fix and see them all processed.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Final checklist

• My code follows the code style of this project found here.
• My change requires a change to the documentation.
• I have read the How to Contribute guidelines.

[SuiteBot]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

j.dang seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}