Skip to main content
Developer Communities Admin
Community Manager
September 15, 2026

Hello, I am working on creating an HR export having both XML and XSLT file.

  • September 15, 2026
  • 5 replies
  • 2 views

Originally posted by Aman Gaur on January 29, 2026 at 12:52 AM.

 

Hello, I am working on creating an HR export having both XML and XSLT file. Mapping on one field is not working; it is giving the exact token value as output in the file. Now what I did is create a new export definition for HR export, but exact same code is giving error.

 

Error:

The job has completed with an error - Input string was not in a correct format.

System.FormatException: Input string was not in a correct format.

  at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)

  at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)

  at SharpTop.DataServices.Platform.Export.HRExport.CeridianHPLEmployeePersonalFileFormatter.ConstructXML(DataTable dataTable, XmlDocument xdoc, XmlElement root) in F:\_wfaz\02\2\s\dayforce\src\HR\ExportFramework.HR\HRExport\Formatters\CeridianHPLEmployeePersonalFileFormatter.cs:line 65

  at SharpTop.DataServices.Platform.Export.HRExport.CeridianHPLEmployeePersonalFileFormatter.Format(String header, String footer, DataTable table, ColumnDefinition[] MetaData) in F:\_wfaz\02\2\s\dayforce\src\HR\ExportFramework.HR\HRExport\Formatters\CeridianHPLEmployeePersonalFileFormatter.cs:line 50

  at SharpTop.DataServices.Platform.Export.HRExport.HRExportEngine.Export(List`1 orgUnits, NamespaceInfo clientNamespace, Boolean testMode) in F:\_wfaz\02\2\s\dayforce\src\HR\ExportFramework.HR\HRExport\HRExportEngine.cs:line 131

  at SharpTop.Engine.BackgroundJobs.HRExport.RunHRExport(Boolean testMode) in F:\_wfaz\02\2\s\dayforce\ServerJobs\BackgroundJobs\HRExport.cs:line 247

--- End of stack trace from previous location where exception was thrown ---

  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

  at SharpTop.Engine.BackgroundJobs.HRExport.RunHRExport(Boolean testMode) in F:\_wfaz\02\2\s\dayforce\ServerJobs\BackgroundJobs\HRExport.cs:line 399

  at SharpTop.Engine.BackgroundJobs.HRExport.Execute() in F:\_wfaz\02\2\s\dayforce\ServerJobs\BackgroundJobs\HRExport.cs:line 82

  at BJE.JobWrapper.<>c__DisplayClass21_1.<CreateJobDelegate>b__0(String x, Int64 y) in F:\_wfaz\02\2\s\dayforce\src\Platform\BJE\JobWrapper.cs:line 418

  at BJE.JobWrapper.<ExecuteAsync>d__19.MoveNext() in F:\_wfaz\02\2\s\dayforce\src\Platform\BJE\JobWrapper.cs:line 172

________________________________________________________________________________

 

 

 

Now why same code is working for one definition and generating file as well (though mapping issue is there) but not on any new HR export definition.

I hope I am clear.

    5 replies

    Developer Communities Admin
    Community Manager
    September 15, 2026

    Originally replied by Eddie Heinzelman on Jan 29, 2026, 3:01 PM.

     

    Aman,

    Would probably need to see your code for this value/field. Does it run without the XSLT? is the token used correct? Is your DataType=String or Number? Troubleshooting xml can take some time.

    Developer Communities Admin
    Community Manager
    September 15, 2026

    Originally replied by Aman Gaur on Jan 30, 2026, 11:28 AM.

     

    Hi Eddie,

    I am attaching my code for your reference; it would be great if you could go through my code specifically for the field:

    <Column Name="LOCATION_CODE" DataType="string" Source="data" Value="position_deptxref"/>.

     

    Output I am getting is in format below:

    col1, col2,Col3------,,Division of Transportation-Administration(this is location code),,col n etc

     

    If you could see my XSLT mapping for LOCATION_CODE- Division of Transportation-Administration is mapped to 15001101-00 but not coming on the file.

     

    Developer Communities Admin
    Community Manager
    September 15, 2026

    Originally replied by Aman Gaur on Jan 30, 2026, 11:30 AM.

     

    https://drive.google.com/drive/folders/18QJqjvUccVunBHYv5fEcYo9v0Wprqlll?usp=sharing

     

    link to my XML file

    Developer Communities Admin
    Community Manager
    September 15, 2026

    Originally replied by Eddie Heinzelman on Jan 30, 2026, 12:40 PM.

     

    Aman,

    Couple issues, but you're going to need to create a new Export Definition.

    The segment you have at the top with the <Options> only applies to Benefits Exports. For an HR Export, you should remove all of that so that it just shows the Filename and then directly into your <Columns>

    The top of your script should look like this (and then all your fields after that seem fine)-

     

    after I made these changes, the XML runs without producing an error. I didn't run it with the XSLT but the error was generating from the XML.

     

    <?xml version="1.0" encoding="utf-8" ?>

    <HRExportConfiguration> <!-- Start HRExportConfiguration Tag -->

    <definitions>

    <FileName>

    <!-- Specify the file naming convention of this export which is provided on the XML Template -->

    <!-- Subject to change if file naming convention for test and prod differs -->

    <!-- File Name XXX can be updated as per the requirement -->

    <Value Value='TEST_CORVEL_' />

    <!-- Datetime Stamp. Can be modified as per the requirement -->

    <Value Value="transaction_timestamp_datetime" Format="yyyyMMddhhmm"/>

    <!-- File extension. XXX can be modified as per the requirement-->

    <Value Value='.csv'/>

    </FileName>

     

    <!-- Start Columns Tag -->

    <Columns>

    <!-- ******************Start Employee Demographics Token****************** -->

     

    Developer Communities Admin
    Community Manager
    September 15, 2026

    Originally replied by Aman Gaur on Jan 30, 2026, 12:50 PM.

     

    Hi Eddie,

    I have tried this also, running XML file as per changes suggested by you is too giving an error.

    Not only on this environment but even on all client environments I am getting same error. Even keeping 1 single column in Export is producing same error. I don't understand what's happening.