![]() Right now it is just saying for each object in string (which doesn’t make any sense).Ĭhange the TypeArgument in the for each property to be String if it isn’t already. That’s how we all learn.Ok, to do that you need to tell uipath that you want to pick up all excel files from that path. I am much more likely to help you if you make an attempt at a problem and post it. This site is as much a learning tool for you as it is for me. Like you, I have a busy life, but I will be sure to get back to you should your comment add value to the post. Please don’t be disheartened by the delay. This is why I review comments before posting them. I like to make sure comments are as valuable as possible for you, the reader, and for myself as a reference. I really enjoy hearing how things are used in the wild.Įnter your email address to subscribe to this blog and receive notifications of new posts by email. Please let me know your thoughts in the comments below. What do you think? Is it too abstract or is it elegant?ĭid this tutorial help you understand the JavaScript one-liner better? Do you think you would apply it in your own projects? ![]() I have an example of how I used the code to check for duplicate selections of files in Google Drive here:Ĭreate a Google Workspace Add-on file picker card with CardService that opens a Google Picker in an overlay window – Google Apps Script ![]() But if I need something in my toolkit to solve a problem like this, then I am definitely going to use it. I don’t think I would use this approach when I need to iterate over objects in the many thousands. I think if I saw something like this in the wild I could pretty easily identify what it was for and see that it was a nice short solution to a problem. It is clean and once I got my head around the Map object, it did make a lot of sense. So should you be using this oneliner over the for loop? Is an impressive one-liner better than something more clear? To be honest, I am on the fence. Which is pretty good compared to some of the other options I found out there. Running a benchmark test with, the one-liner ran only 13.74% slower. ![]() Surprisingly better than I thought it would, to be honest. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |