| aultmike |
| Member |
|
| 44708 |
|
|
| None Specified |
|
| Tuesday, November 3, 2009 |
| Thursday, September 26, 2013 2:21:53 PM |
17
[0.09% of all post / 0.00 posts per day] |
|
|
Does DiffDog offer some form of API so that it could be used programmatically? For instance if I wanted to write a C# app that compared two xml files and displayed the differences.
|
Is there any way I can set a property in the MapForce map that will persist itself to the xslt as a comment? I'm thinking I would like to be able to specify a date compiled or a version number...
Thanks
|
|
Duuuuuuuuude! Thats awesome! Thank you for taking the time to reply. :) Thats much more elegant than what I did. If there was a way I could, I would give you a gold star or upvote your post. Thanks again!
|
Lets say I have a string like so: 123-45-6789 and I want to replace the - with a space. How would I best accomplish this in XSLT 1.0. Right now I'm thinking I would have to split the string into three pieces and then concat them back together... Any ideas?
Thanks
|
|
Where did you guys land on this? I'm noticing the same thing and was curious as to what it meant. Thanks
|
|
Is it necessary to Un-install the current version of XmlSpy, Mapforce, etc when I want to install a new version?
|
|
I've noticed that when I have an input file specified for and XSD and I change the contents of the input file, those changes arent reflected in mapforce until I reload the mfd... has anyone else ran into this?
|
Here is the reply I received from Altova. Just FYI.
I can only imagine that this has to do with the fact that internally the xpath datatype number stores the value as a floating point number and that this might account for the value not being exactly the same as the string passed to the number function. I don't think this is a bug however as I tested the transformation with another engine as well (msxml) and got the same result. I will have to enquire with the developer responsible for the xpath implementation whether he can clarify the result. Is it possible for you to use xslt 2.0 as a workaround or change the datatype in the target schema of your mapping from long to string?
In the end I ended up changing the type of the field in the destination schema.
|
|
Hello, My source xsd has a field typed as a string... I am directly mapping this field to my destination xsd whose field is typed as a long... I've noticed that the number in the source field get slightly modified when it gets mapped to the destination field when I use run the XSLT. Any Idea why this happens?
|
|
I understand that I can design multiple mappings in the same file but there is no way to specify the name of each XSLT that will be generated?
|
|
