I'm starting a project where I have to work with XML files, and when I search for a video, I see that yours was published 5 hours ago. I'm a lucky guy. Thank you."
Thanks for a clear and concise tutorial on how to work this stuff. I find the namespace stuff tedious to work with, so I have, in the past, stripped out the namespace declaration from the text before deserializing the XML. It's a tip, not a recommendation. That isn't always a wise thing to do, especially if your XML document is complex and contains vaguely similar data from multiple sources. Remember, the namespace stuff is there to remove ambiguity, not just to be a pain in the arse.
Thank you for your tips. I would like more content about xml file like doing a loop to extract all the value for an element or how to get the name of the customer(s) where state is equal to NY
@@UiPathwithJeppe hi, I have a perfect senario for you: imagine you have just finish an automation and you want some help to create the documentation. You wants to create a RPA capable of opening xaml files and put in an excel file all the variable (name and type) and arguments (name, type, direction and variable value) for each xaml of the project. :-)
I'm starting a project where I have to work with XML files, and when I search for a video, I see that yours was published 5 hours ago. I'm a lucky guy. Thank you."
We were meant for each other 😀
@@UiPathwithJeppe Definitely!!!!!
@@LuizFernandoDealerIntelligence 🤣
Another fantastic relevant video for the UiPath Community!
@@Steve-yq5fh thanks a lot, very much appreciated 🙏🙏
Another super informative video! Thanks! 🙂
Thank you (again), Paul. My pleasure, absolutely.
Thanks for a clear and concise tutorial on how to work this stuff.
I find the namespace stuff tedious to work with, so I have, in the past, stripped out the namespace declaration from the text before deserializing the XML. It's a tip, not a recommendation.
That isn't always a wise thing to do, especially if your XML document is complex and contains vaguely similar data from multiple sources. Remember, the namespace stuff is there to remove ambiguity, not just to be a pain in the arse.
Yeah, stripping the namespaces have crossed my mind, too. Not saying if I've done or not ;-)
...and thanks for the kind words, much appreciated.
Thank you for your tips. I would like more content about xml file like doing a loop to extract all the value for an element or how to get the name of the customer(s) where state is equal to NY
Just added it to my list. Stay tuned. Next week, most likely. Feel free to suggest more scenarios. 👍
@@UiPathwithJeppe hi, I have a perfect senario for you: imagine you have just finish an automation and you want some help to create the documentation. You wants to create a RPA capable of opening xaml files and put in an excel file all the variable (name and type) and arguments (name, type, direction and variable value) for each xaml of the project. :-)
@@oliviergarcin8624 something like this?
ruclips.net/video/MILLNO0r6k4/видео.html