Unless you WANT to throw the error, always be sure to use conditional json syntax...there is always a chance a file may not be present and the data flow property may not be present. Additionally: To save money, you can concatenate and capture those metrics all together in one set variable activity, put an @json expression in front of your expression, and parse your json values downstream, but I do get and understand the want to capture and report each metric independently in its own fixed column--especially if you are a Kimball Toolkit disciple of the Audit dimension 😊. I have also seen others write generic key value pairs as ETL metrics in a relational model as well. Depends on your use case.
@@AllAboutBI Thank you for your videos. Can you please create one video on extract the file from share point and load into the sql table. It will be helpful.
Must watch for all the beginners.
Nice session 🎉
As usual 👍👌 super mam
Thank you
Unless you WANT to throw the error, always be sure to use conditional json syntax...there is always a chance a file may not be present and the data flow property may not be present.
Additionally: To save money, you can concatenate and capture those metrics all together in one set variable activity, put an @json expression in front of your expression, and parse your json values downstream, but I do get and understand the want to capture and report each metric independently in its own fixed column--especially if you are a Kimball Toolkit disciple of the Audit dimension 😊. I have also seen others write generic key value pairs as ETL metrics in a relational model as well. Depends on your use case.
Agreed! 👍
@@AllAboutBI Thank you for your videos. Can you please create one video on extract the file from share point and load into the sql table. It will be helpful.