Bresleveloper Digital - the best at SharePoint, PowerApps and Office365, Contact us now!

Full Code in the end! :) Assuming you have some connection string: private static string ConnectionString = ConfigurationManager.AppSettings["myConnStrApp"]; And assuming we are using the simple "SqlDataAdapter", our Method will start with: using (SqlConnection conn = new SqlConnection(ConnectionString)) {       using (SqlDataAdapter adp = new SqlDataAdapter("SELECT * FROM " + tblname, conn)) {             DataSet ds = new DataSet("ds");             adp.Fill(ds); We have 2 generic options return (convert to) Json String build json object Lets 1st mention the "standard" way - by class model. That means we need to create a new C# class per sql table, and then create matching parsing mechanism, meaning that the rest of our method contains this (see more in the end): var rows = ds.Tables[0].Rows; for (int i = 0; i < rows.Count; i++) {     var r = rows[i];     t.Add(new TNG() {         Id = int.Parse(r["Id"].ToString()),        

Important   if you get an error that says: powerapps patch sharepoint list error the specified column "" does not exist the column with the most similar name is "" that would be because you use the column DisplayName instead of the InternalName Solution:  Set(oItem, {     Title:me.displayName,     EmpITref:{Id:meSP.ID, Value:meSP.Title},     EducationLevel:EducationLevel.SelectedText.Value,     CertCount:vis,     WorkYearsExp:WorkYearsExp.SelectedText.Value,     anythingElse:anythingElse.Text,     DigitalSignature:DigSign.Text }); If(vis<>0, Set( oItem, Patch (oItem, {     Cert1_x002d_OrgAd:cert1_orgAd.Text,      Cert1_x002d_Title: cert1_title.Text,     Cert1_x002d__x0023_:cert1_No.Text,      Cert1_x002d_GrantDate:cert1_grant.SelectedDate,     Cert1_x002d_exp_x002e_Date:cert1_exp.SelectedDate }))); If(vis=2, Set( oItem, Patch (oItem, {     Cert2_x002d_OrgAd:cert2_orgAd.Text,      Cert2_x002d_Title: cert2_title.Text,     Cert2_x002d__x0023_:cert2_No.Text,     

 Scenario: there is a new SP sub-folder every day with some files. this needs to be shared to about 40 different emails daily. BUT with 2 exclusions: 1. sometimes we want these 35 emails, sometimes some other 38 emails. so every day we exclude a few emails, every day different ones. 2. we do not want the "clients" to know about one another, so no bulk sharing or just external link, only share 1 by 1. SOLUTION: 1. SPList for emails ("clients") 2. SP Library containing "main" folder, inside we create daily SP sub-folder with a name (usualy just the date like "25.8.23") 3. SPList for trigger the flow (power automate) on item created, getting from+archive for daily broadcast 4. flow for filtering out excluded emails, and sending 1 by 1 a share email. lets go 1. SPList for emails ("clients") really nothing other than new list, Title for "client name" and another text field for email 2. SP Library containing "main" folder,