jenlion
IS-IT--Management
- Nov 13, 2001
- 215
I have an xml file that I am transforming via xslt into another xml file. The new xml file must be in a particular format in order for a calling program to load data, so the xslt is putting it into that format.
I need the xslt to preserve null values, though. Right now, if there's no value for <PHONE></PHONE> in the original xml file, then it just skips it in the resulting file. But I need it to keep it there, just <PHONE></PHONE>, or the program importing the file fails.
I used Altova's MapForce to create the xslt, since I'm new to this, but I don't see an option to "force keeping null values" or anything like that, so I am wondering if there's an option for this in general that I can use in the xslt.
Also -- sometimes my resulting file uses the alternate <PHONE /> instead. Importing program barfs on that too. Any way to force it to <PHONE></PHONE> in regular xslt? Happy to modify my generate xslt with whatever I need.
I need the xslt to preserve null values, though. Right now, if there's no value for <PHONE></PHONE> in the original xml file, then it just skips it in the resulting file. But I need it to keep it there, just <PHONE></PHONE>, or the program importing the file fails.
I used Altova's MapForce to create the xslt, since I'm new to this, but I don't see an option to "force keeping null values" or anything like that, so I am wondering if there's an option for this in general that I can use in the xslt.
Also -- sometimes my resulting file uses the alternate <PHONE /> instead. Importing program barfs on that too. Any way to force it to <PHONE></PHONE> in regular xslt? Happy to modify my generate xslt with whatever I need.