I am updating ACA Employer Maintenance for the 2019 calendar year. After updating fields, will not save, message is "year is required". Anyone else having this issue?
I am updating ACA Employer Maintenance for the 2019 calendar year. After updating fields, will not save, message is "year is required". Anyone else having this issue?
I manually replaced the file as suggested by support now the client is getting it on the affiliated entry page.
I called Sage and they suggested replacing the PR_ACAEmployer.m4t with a working copy.
Rebuilding the file or reinitializing it did not work, but the copy from the ABC company did work. I was thinking…
Also, just as a side note. I have already updated all employees with their appropriate ACA information for 2019.
There is a knowledge base article on this issue and you have to rebuild data file layouts (I think).
This might be the KB article referenced https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=95595&sliceId=1&isLoadPublishedVer=&docType=kc&docTypeID=DT_Article&stateId=12703&cmd=displayKC&dialogID=516415&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl&openedFromSearchResults=true
Did you get this fixed? I was going in to fix it for a customer and the fix isn't working for me.
Yes, I called Sage customer service and they logged in remotely and installed one file and it fixed the situation. I know that is not a do-it-yourself solution, but it worked.
I called Sage and they suggested replacing the PR_ACAEmployer.m4t with a working copy.
Rebuilding the file or reinitializing it did not work, but the copy from the ABC company did work. I was thinking it could just be an issues with upgraded companies but creating a company from scratch also did NOT work.
In my test system I'm completely removing Sage 2019 and reinstalling to see if it is actually an issue with my(and the client's) install or a program issue.
This has been submitted to Sage Engineering and they are in the process of researching and finding a solution currently. KB 95595 has this workaround however engineering will be looking for a better workaround.
I manually replaced the file as suggested by support now the client is getting it on the affiliated entry page.
*Community Hub is the new name for Sage City