How to properly process csv files in Power Automate-Encodian Parse CSV

Поделиться
HTML-код
  • Опубликовано: 18 окт 2024

Комментарии • 13

  • @vxmine
    @vxmine 2 года назад

    Good video! I'm in this situation now, I need to do some CSV to Excel. I could research and mess around with building my own, but for around 10 flow runs per month, services like these will save me time. Thanks!

  • @AalimOnlineOfficial
    @AalimOnlineOfficial Год назад

    Great

  • @sashawarchoon1989
    @sashawarchoon1989 3 года назад

    csv parsing must be standard functionality made available to everyone by Microsoft I believe.
    I've used couple other tutorials available in RUclips to build flows with csv parsing. As long as I know that I'm not going to have all these symbols and characters that can break my flow down I'm good.
    Honestly, instead showing how to use Encodian I would prefer you Ali to show how to do it yourself (all these workarounds). Your channel is known for such technical insights not for promoting 3rd parties ;)

    • @AlirezaAliabadi
      @AlirezaAliabadi  3 года назад

      You got it. I will make a video soon and show you how I make it myself if not using Encodian or any third party 🙂

    • @joelmalepe4862
      @joelmalepe4862 2 года назад +1

      @@AlirezaAliabadi i follow your videos. Has this been uploaded yet?

    • @SiyamandRashid
      @SiyamandRashid Год назад

      @@joelmalepe4862 Hello Ali, did you upload this video please?

    • @SiyamandRashid
      @SiyamandRashid Год назад

      @@AlirezaAliabadi
      Hello Ali, did you upload this video please?

  • @hasanradi93
    @hasanradi93 2 года назад

    I'm not like this method to use third party to solve the problem.

    • @raahulc8649
      @raahulc8649 Год назад

      is there any other method to solve this?

  • @encodian
    @encodian 2 года назад

    Thanks @AlirezaAliabadi for taking the time to share with the community how the Encodian connector can help with CSV parsing.
    We've only just picked this up so there has been no paid promotion here, just an expert sharing an option with the community :)
    We're a Microsoft ISV and Services partner and our role (as any other) is to help organizations realize benefits from the their technology investments (Fiscal, compliance, compete, service, etc.), and like any other vendor, we're attempting to add value to the M365 platform to simplify deployment and onward support, reduce cost, increase speed of delivery, etc.
    Phil raises some excellent points for consideration!
    Taking a solution architect viewpoint; it's always good to have options, configuration vs code, code vs 3rd party COTS... choosing which way to go depends on many factors (delivery speed, cost, operational management (inc support), strategy (short & long)... options are a good thing and sharing these options is also a good thing :)
    Thanks again @AlirezaAliabadi

  • @Worrelpa
    @Worrelpa 3 года назад

    I think what puts people off these third party connectors / services are several factors.
    Can they do the job most definitely.
    Are they expensive and do you get full value out of them. Well not for one flow, but maybe for several.
    Where does my data go and is is secure and does anyone store it when they shouldn't. Though that is usually covered I. Agreements it is still a concern transmitting data outside you tenant or systems. Does it cross any borders that data under regulatory compliance shouldn't cross.
    The third party you use. Will they be around in 6 months to a year or more when you need them.
    What is the companies support like?
    All questions people should ask before dropping the money.
    Not saying not to
    Just things people need to consider
    I do wish there were more shoe cases on third party connectors
    There are some good ones out there.

    • @AlirezaAliabadi
      @AlirezaAliabadi  3 года назад +1

      I am 100% with you on that. As much as I wanted to get there, I decided to keep the content technical with respect to my typical audience.
      The main message here is, parsing CSV takes a lot more than a few loops and splits that one can handle it inside Power Automate. 🙂