on 2025 Mar 19 11:01 PM
Since Centralized Services has taken over the population of job entry/position entry dates,etc. calculations there's been an issue I haven't been able to get past. At go-live most companies will not have history to the extent necessary to have valid entry dates. Is there a workaround I'm not aware of for this? If not, this seems like a pretty major flaw.
Request clarification before answering.
Hello,
According to KBA 3063678 - Entry Date Field Logic via Centralized Services
which means the standard fields of the entry-date are set automatically by the system once the relevant fields are changed. That is to say, the entry-date fields could not be changed if the relevant fields are not changed.
If your business need requires an Entry Date field, whose calculation deviates from the system logic, a custom date field can be used for this purpose. You can follow the steps provided in KBA 3063678 - Entry Date Field Logic via Centralized Services
Hope the answer helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
5 | |
4 | |
2 | |
2 | |
2 | |
2 | |
2 | |
2 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.