Forum Discussion
Hi @Raph,
It’s very simple. You just need to not map the columns manually, i.e use from a Mapper this expression
$.mapValues((value,key) => value) into $ as target and that’s all.
Attached is a pipeline
Original order for columns_2020_10_24.slp (3.4 KB)
/Igor
I tried this suggestion. I am sorry I don’t understand what you meant. The mapper generates an error. The snaps used for test were as follows: Filreader > Parser > Mapper (.mapValues((value,key)=>value) > Excel Formatter > File Writer.
The columns run from A…GM
Can you clarify a little please?
- jbaldetti9 years agoFormer Employee
Workday publishes some WSDLs in the Workday Services documentation site without a valid endpoint for the purpose of reference. This can be verified by opening the WSDL file and look at the soap address location at the bottom of the WSDL. A valid endpoint for workday should have a location starting with the “https://” protocol.
Here is an example of a valid endpoint at the end of the WSDL file:
…
<wsdl:service name=“Human_ResourcesService”>
<wsdl:port name=“Human_Resources” binding=“wd-wsdl:Human_ResourcesBinding”>
<soapbind:address location=“https://impl-cc.workday.com/ccx/service/osv_fusionio4/Human_Resources/v18”/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>If it does not have the “https://”, then the solution would be to export the Workday WSDL from the Workday tenant.
The Workday snap is a preferable over the SOAP snap since it is an easier to use and more capable.