Hi Amit Thorve,

Please find below details.

Concern: When I ran this file twice, I am still getting terms on the file.

Cause: We have checked and found Stop Date MM field has mapping of termination date and it has field level attribute
If termination date is populating on file then take month of that field using start and end length otherwise take 12 as null replacement character. same for Stop Date YYYY it take year and has 2017 null replacement character.Please find below snap.

In between Stop Date MM and Stop Date YYYY field there is hard coded value as "/', "15", "/" due to this its roll out 12/15/2017 as termination date on second export as hard coded value.
Please find below snap.

Please let me know if require more details.

CC-Vinayak Kulkarni,Rajendra Pawar,Rakesh Shahane

Thanks,
Ganesh

Now the global feed started giving an error.

Prashant Samal Please check this.

Hello Amit,

I tried looking into this by changing some attributes on test template but facing error while exporting:

There seems some code issue please find below error log

ErrorID : 0
ErrorSource : ControllerAppTier.Save->WORKTERRAControllerAppTier.Save->ExecuteExportDTS.ExportData_Isolated->WTIsolatedRoutines.Main->ExecuteExportDTS.ExportData->ExportProcessRowwise.ExportData->ExportProcessRowwise.ProcessDataForExport->ExportProcessRowwise.ProcessEachSubtemplate->ExportProcessRowwise.WriteRecordIntoExportFile
ErrorMessage: Index was outside the bounds of the array.
StackTrace: at WORKTERRA.Shared.WORKTERRAControllerAppTier.Save(WORKTERRAControllerWebTierEntity objWORKTERRAControllerWebTierEntity)
at WORKTERRA.ControllerAppTier.Save(Int32 intProjectsId, String strInput)
TargetSite: System.String Save(WORKTERRA.Shared.WORKTERRAControllerWebTierEntity)

Thanks
S Prashant.
____________________________________

Amit Thorve Ganesh Sadawarte Vinayak Kulkarni

Hi Amit Thorve,

Please find below 3C's,

Concern: Server error occurred while exporting template.

Cause: We have checked this and found that there was field level IsPaddingRequired attribute applied for Monthly Amount field for all company level templates but no leading and trailing value provided. Due to its throwing server error. As we are not allowing to save blank value through UI so we need to check how this get save. Please find snap.

Correction: We need provide value either for leading or trailing.

Please let us know if you need any other details.

CC-Samir,Satya,Vinayak Kulkarni,Rajendra Pawar

Thanks,
Ganesh

Hi Aniruddha,

Can you check if we can have padding required with blank leading and trailing values? and if yes then are we getting server error while exporting template? Thanks.

Aniruddha Dev, Rajendra Pawar, Ganesh Sadawarte Whatever comment Ganesh mentioned above is not correct.

I have not changed a single settings for this field then why suddenly it started giving an error? I just changed the Term date default value from 2017 to 2018.

Please compare the templates with 2017 template for any other issue.

Hi Amit Thorve

As discussed, we have updated leading values for monthly amount field as Space (' ') for all 2018 templates. Please check and let us know if error still persist. Thanks.

Vinayak Kulkarni, Ganesh Sadawarte, Rajendra Pawar

Thanks for running the script. I am able to run the file now.

I have few points which needs to be checked ASAP.

1. The Start date came out as blank for 75% of the records. The start date column is mapped to “Pay period date for election effective date”.
2. For around 22-25% records the start date is in 2016.
3. For around 190 records the start date is in 2017.

Hi Amit,

We have checked this, This field populates from back-end table in which there was no entry for year 2018. We have added entries for year 2018 now.
Please check and let us know if you face any other issues with this file.

Back-end table name: SBMPayrollDateMatrixForExport
Attached BackEndEffectiveDateForCOB.xls file contains all entries, Entries which are highlighted yellow are added for year 2018. Please check.

Thanks,
Vinayak

Ganesh Sadawarte and Vinayak Kulkarni Thanks for updating this table.

Can you please tell me why the 2016 effective dates and 2017 dates (other than 12/16/2017) with different values are rolling out on the file?

Hi Amit Thorve,

As discussed there were some enrollment effective for ex(12/01/2017, 11/01/2017) and rates also effective from same date with 12/31/2018 termination date. So as per SBM table date it populated on file.

CC-Vinayak Kulkarni

Thanks
Ganesh