cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
whitekn3
Regular Visitor

What types of apps is PowerApps appropriate for?

I have a lot of experience with Access VBA, C++ development, and limited experience with C# and XAMARIN Forms.  I am brand new to PowerApps.  I am interested in learning more about PowerApps and have a project that would involve about 10 lookup  tables, 4 or 5 main tables, Two moderate forms  (Sub forms, simple code), and several single table minor forms for maintaing the lookup tables. 

 

Does this sound like something  PowerApps could handle?

 

Any limitations? Gotchas? I ought to be aware of before using PowerApps?  At what level of complexity does it choke?

32 REPLIES 32

Can you write a Zero Length string back to the Azure SQL Database?  (I haven't used Azure SQL, but I'm assuming you can set a DISALLOW_ZERO_LENGTH constraint on the Azure SQL table.column and that it would not be set for the column in  question.)

 

If so, that would be acceptable for my purposes.  Having to write a dummy value, such as '_NA' would not make me happy.  My experience has been that such data often creates additional complexity in the code and SQL.

 

As I'm considering PowerApps for "simple" field updates of data also used by very complex desktop apps I can't easily change the tables.

Anonymous
Not applicable

@JRaasumaa

Well, with all due respect I am infinitely familiar with the definition of Null, and Zero Length strings for that matter.

Not sure you understood what I posted - what I was saying?

 

 

Also:

"it's just not supported to write the value Null to a field in SQL"

You are referring only to Azure SQL, correct? Because it certainly is supported in non Azure (eg on prem) SQL Server databases. If it's not supported in Azure, it certainly should be.  I *never* use ZLS or allow ZLS in any field (this is an option in Access).

 

Regarding:

"You could write your app to write a blank value "" or 0 to an integer field etc"

Sorry, but that is not good practice.  A ZLS is of course not the same as a Null, and they are visually indistinguishable - which can result in a lot of confusion in queries where you have criteria against a field that is supposed to be (ie expected to be) Null, but someone has entered a ZLS. oops!

And substituting a zero (0) in an integer field that is supposed to be Null ... similar problem.  Now you are putting real data (0) in a field that s/b (ie expected to be) Null.

 

I have not yet (but soon) worked with an Azure SQL db to confirm any of this.

Hi @JRaasumaa IMHO it is a bug.  Once a field is set to a non-null value, then it cannot be set back to a null value by PowerApps.  This is not a limitation of Azure SQL Database, which works perfectly.

 

The documentation for the Blank() function clearly admits this is a limitation (euphemism for bug):

"Note: At this time, storing blank values is supported only for local collections. We know that many data sources support blank (NULL) values, and we're working to lift this limitation."

 

"" is not the same as null, and 0 is also not the same as null

 

Hi @whitekn3, yes you can write back a "" to Azure SQL Database.

It is a work-around, but hopefully at some point we will be able to use blank.

I fully agree with @Anonymous


@Anonymous wrote:

@JRaasumaa

Well, with all due respect I am infinitely familiar with the definition of Null, and Zero Length strings for that matter.

Not sure you understood what I posted - what I was saying?

 

 

Also:

"it's just not supported to write the value Null to a field in SQL"

You are referring only to Azure SQL, correct? Because it certainly is supported in non Azure (eg on prem) SQL Server databases. If it's not supported in Azure, it certainly should be.  I *never* use ZLS or allow ZLS in any field (this is an option in Access).

 

Regarding:

"You could write your app to write a blank value "" or 0 to an integer field etc"

Sorry, but that is not good practice.  A ZLS is of course not the same as a Null, and they are visually indistinguishable - which can result in a lot of confusion in queries where you have criteria against a field that is supposed to be (ie expected to be) Null, but someone has entered a ZLS. oops!

And substituting a zero (0) in an integer field that is supposed to be Null ... similar problem.  Now you are putting real data (0) in a field that s/b (ie expected to be) Null.

 

I have not yet (but soon) worked with an Azure SQL db to confirm any of this.

 

 

 

@Anonymous With all due respect your post made it sound like you did not which is why I tried to explain it to you. Writing a blank value or a 0 could absolutely be good practice if your data sets and filtering work to adjust for this. It depends on the circumstances of the app and what I gave was a perfectly acceptable solution to the fact that Null cannot be written in certain situations, in fact we use blank fields all the time for a string and it works absolutely fine. We also use a 0 in cases that the value should either be Null, 0 or always greater than 0, there is nothing wrong with that specific data set having a 0 instead of a Null and the filtering we use in PowerApps plans for this.

 

All of this literally depends on the app and data that's being worked on, my suggestion and solution works.

 

 


@Meneghino wrote:

Hi @JRaasumaa IMHO it is a bug.  Once a field is set to a non-null value, then it cannot be set back to a null value by PowerApps.  This is not a limitation of Azure SQL Database, which works perfectly.

 

The documentation for the Blank() function clearly admits this is a limitation (euphemism for bug):

"Note: At this time, storing blank values is supported only for local collections. We know that many data sources support blank (NULL) values, and we're working to lift this limitation."

 

"" is not the same as null, and 0 is also not the same as null

 


@Meneghino

 

It's not a bug in that the software is doing exactly what it is supposed to, it's a limitation.

 

A limitation is not a bug, it's the current design of the software, not a flaw, error, fault or failure of the software (bug).

 

Because of this my suggestion was a workaround that is a perfectly acceptable solution depending on the data and the app to resolve this. Please see my post above.

 

 

Anonymous
Not applicable

Here is another perspective:

In working with Microsoft Access for 25 years now, Access handles and supports Nulls quite well.

In a Table, when you define a new Field's Data Type as Number, Text, Memo, DateTime and a couple of others, unless you explicitly set a Default Value at the Table Level, the initial value of that field in each row is Null. Additionally for a Text Data Type, you can specifiy 'Allow Zero Length', which I would rarely do (importing data into this field from Excel might be an exception).

 

So at any time when updating a given Field (of the types noted above), you can write real data or a Null. You can overwrite real data with a Null, or vice-versa.

 

This is certainly the same case for SQL Server, as I do this all the time.  However, I cannot (yet) speak for an Azure SQL db. But I find it hard to believe Azure does not work the same way.

 

So maybe we are all talking about something different. And there is some anamoly in PowerApps regarding Nulls and Azure. But if for whatever reason from within PowerApps you cannot write a Null to an Azure SQL db Field (eg a Text Data Type) - even though when defining that field it will initially be Null ... that ... is a serious problem, bug or otherwise.

 

 

 

 

Anonymous
Not applicable

@Meneghino

RE: " Once a field is set to a non-null value, then it cannot be set back to a null value by PowerApps."

So ... if this is the case ... then this is *definitely* a SERIOUS problem, bug or otherwise. So I totally agree.

 

Meanwhile though... writing a zero (0) or "" etc., as a workaround ... when a Null s/b written (if that is the case), then you are basically writing 'fake data' .. which is bound to bite one in the ass down the road, especially when it comes to querying that data for a report, etc., and criteria is filterering for and expecting a Null ... OOPS !

 

Microsoft needs to address this (basic) issue ASAP if not sooner.

 

 


@Anonymous wrote:

Here is another perspective:

In working with Microsoft Access for 25 years now, Access handles and supports Nulls quite well.

In a Table, when you define a new Field's Data Type as Number, Text, Memo, DateTime and a couple of others, unless you explicitly set a Default Value at the Table Level, the initial value of that field in each row is Null. Additionally for a Text Data Type, you can specifiy 'Allow Zero Length', which I would rarely do (importing data into this field from Excel might be an exception).

 

So at any time when updating a given Field (of the types noted above), you can write real data or a Null. You can overwrite real data with a Null, or vice-versa.

 

This is certainly the same case for SQL Server, as I do this all the time.  However, I cannot (yet) speak for an Azure SQL db. But I find it hard to believe Azure does not work the same way.

 

So maybe we are all talking about something different. And there is some anamoly in PowerApps regarding Nulls and Azure. But if for whatever reason from within PowerApps you cannot write a Null to an Azure SQL db Field (eg a Text Data Type) - even though when defining that field it will initially be Null ... that ... is a serious problem, bug or otherwise.

 

 

 

 


 

I think it's great you've worked in MS Access for 25 years, I too have had decades of experience in databases and programming languages (but I don't give myself a nickname based on it), but keep in mind, this is not MS Access.

 

Putting a "" or a 0 into a column is NOT "fake" data (as you say in another post) IF the data set warrants this type of a workaround. There is NOTHING wrong with doing this as a resolution. It would be great if you focus on that instead of shouting that it's not a real Null. Depending on the data you may not need to write a Null and can work around this current limitation with this workaround and I will continue to offer up as a solution to people who need help with this.

 

Hopefully they resolve this limitation soon but for now there are certainly ways for people to work around it depending on their data, lets all focus on helping people with workarounds and pushing Microsoft and the PowerApps team to coming up with solutions to this products current limitations.

 

 

 

 

Anonymous
Not applicable

"Shouting" ?

Really ?   So, I'm shouting because I do not agree with you ?

 

And I understand you have an opinion and I have mine. That's how the world works.

Sorry you have a problem with my username, nothing this is not the only forum I participate in. (Google DatabaseMX and Experts-Exchange.com 🙂 )

So ... within this thread, the score stands as follows:

Bug:   2

Not Bug (limitation):  1

 

Bug/Llimitiation ...I suppose it's all the same in the end.

Helpful resources

Announcements

Exclusive LIVE Community Event: Power Apps Copilot Coffee Chat with Copilot Studio Product Team

  It's time for the SECOND Power Apps Copilot Coffee Chat featuring the Copilot Studio product team, which will be held LIVE on April 3, 2024 at 9:30 AM Pacific Daylight Time (PDT).     This is an incredible opportunity to connect with members of the Copilot Studio product team and ask them anything about Copilot Studio. We'll share our special guests with you shortly--but we want to encourage to mark your calendars now because you will not want to miss the conversation.   This live event will give you the unique opportunity to learn more about Copilot Studio plans, where we’ll focus, and get insight into upcoming features. We’re looking forward to hearing from the community, so bring your questions!   TO GET ACCESS TO THIS EXCLUSIVE AMA: Kudo this post to reserve your spot! Reserve your spot now by kudoing this post.  Reservations will be prioritized on when your kudo for the post comes through, so don't wait! Click that "kudo button" today.   Invitations will be sent on April 2nd.Users posting Kudos after April 2nd. at 9AM PDT may not receive an invitation but will be able to view the session online after conclusion of the event. Give your "kudo" today and mark your calendars for April 3rd, 2024 at 9:30 AM PDT and join us for an engaging and informative session!

Tuesday Tip: Unlocking Community Achievements and Earning Badges

TUESDAY TIPS are our way of communicating helpful things we've learned or shared that have helped members of the Community. Whether you're just getting started or you're a seasoned pro, Tuesday Tips will help you know where to go, what to look for, and navigate your way through the ever-growing--and ever-changing--world of the Power Platform Community! We cover basics about the Community, provide a few "insider tips" to make your experience even better, and share best practices gleaned from our most active community members and Super Users.   With so many new Community members joining us each week, we'll also review a few of our "best practices" so you know just "how" the Community works, so make sure to watch the News & Announcements each week for the latest and greatest Tuesday Tips!     THIS WEEK'S TIP: Unlocking Achievements and Earning BadgesAcross the Communities, you'll see badges on users profile that recognize and reward their engagement and contributions. These badges each signify a different achievement--and all of those achievements are available to any Community member! If you're a seasoned pro or just getting started, you too can earn badges for the great work you do. Check out some details on Community badges below--and find out more in the detailed link at the end of the article!       A Diverse Range of Badges to Collect The badges you can earn in the Community cover a wide array of activities, including: Kudos Received: Acknowledges the number of times a user’s post has been appreciated with a “Kudo.”Kudos Given: Highlights the user’s generosity in recognizing others’ contributions.Topics Created: Tracks the number of discussions initiated by a user.Solutions Provided: Celebrates the instances where a user’s response is marked as the correct solution.Reply: Counts the number of times a user has engaged with community discussions.Blog Contributor: Honors those who contribute valuable content and are invited to write for the community blog.       A Community Evolving Together Badges are not only a great way to recognize outstanding contributions of our amazing Community members--they are also a way to continue fostering a collaborative and supportive environment. As you continue to share your knowledge and assist each other these badges serve as a visual representation of your valuable contributions.   Find out more about badges in these Community Support pages in each Community: All About Community Badges - Power Apps CommunityAll About Community Badges - Power Automate CommunityAll About Community Badges - Copilot Studio CommunityAll About Community Badges - Power Pages Community

Tuesday Tips: Powering Up Your Community Profile

TUESDAY TIPS are our way of communicating helpful things we've learned or shared that have helped members of the Community. Whether you're just getting started or you're a seasoned pro, Tuesday Tips will help you know where to go, what to look for, and navigate your way through the ever-growing--and ever-changing--world of the Power Platform Community! We cover basics about the Community, provide a few "insider tips" to make your experience even better, and share best practices gleaned from our most active community members and Super Users.   With so many new Community members joining us each week, we'll also review a few of our "best practices" so you know just "how" the Community works, so make sure to watch the News & Announcements each week for the latest and greatest Tuesday Tips!   This Week's Tip: Power Up Your Profile!  🚀 It's where every Community member gets their start, and it's essential that you keep it updated! Your Community User Profile is how you're able to get messages, post solutions, ask questions--and as you rank up, it's where your badges will appear and how you'll be known when you start blogging in the Community Blog. Your Community User Profile is how the Community knows you--so it's essential that it works the way you need it to! From changing your username to updating contact information, this Knowledge Base Article is your best resource for powering up your profile.     Password Puzzles? No Problem! Find out how to sync your Azure AD password with your community account, ensuring a seamless sign-in. No separate passwords to remember! Job Jumps & Email Swaps Changed jobs? Got a new email? Fear not! You'll find out how to link your shiny new email to your existing community account, keeping your contributions and connections intact. Username Uncertainties Unraveled Picking the perfect username is crucial--and sometimes the original choice you signed up with doesn't fit as well as you may have thought. There's a quick way to request an update here--but remember, your username is your community identity, so choose wisely. "Need Admin Approval" Warning Window? If you see this error message while using the community, don't worry. A simple process will help you get where you need to go. If you still need assistance, find out how to contact your Community Support team. Whatever you're looking for, when it comes to your profile, the Community Account Support Knowledge Base article is your treasure trove of tips as you navigate the nuances of your Community Profile. It’s the ultimate resource for keeping your digital identity in tip-top shape while engaging with the Power Platform Community. So, dive in and power up your profile today!  💪🚀   Community Account Support | Power Apps Community Account Support | Power AutomateCommunity Account Support | Copilot Studio  Community Account Support | Power Pages

Super User of the Month | Chris Piasecki

In our 2nd installment of this new ongoing feature in the Community, we're thrilled to announce that Chris Piasecki is our Super User of the Month for March 2024. If you've been in the Community for a while, we're sure you've seen a comment or marked one of Chris' helpful tips as a solution--he's been a Super User for SEVEN consecutive seasons!       Since authoring his first reply in April 2020 to his most recent achievement organizing the Canadian Power Platform Summit this month, Chris has helped countless Community members with his insights and expertise. In addition to being a Super User, Chris is also a User Group leader, Microsoft MVP, and a featured speaker at the Microsoft Power Platform Conference. His contributions to the new SUIT program, along with his joyous personality and willingness to jump in and help so many members has made Chris a fixture in the Power Platform Community.   When Chris isn't authoring solutions or organizing events, he's actively leading Piasecki Consulting, specializing in solution architecture, integration, DevOps, and more--helping clients discover how to strategize and implement Microsoft's technology platforms. We are grateful for Chris' insightful help in the Community and look forward to even more amazing milestones as he continues to assist so many with his great tips, solutions--always with a smile and a great sense of humor.You can find Chris in the Community and on LinkedIn. Thanks for being such a SUPER user, Chris! 💪🌠

Find Out What Makes Super Users So Super

We know many of you visit the Power Platform Communities to ask questions and receive answers. But do you know that many of our best answers and solutions come from Community members who are super active, helping anyone who needs a little help getting unstuck with Business Applications products? We call these dedicated Community members Super Users because they are the real heroes in the Community, willing to jump in whenever they can to help! Maybe you've encountered them yourself and they've solved some of your biggest questions. Have you ever wondered, "Why?"We interviewed several of our Super Users to understand what drives them to help in the Community--and discover the difference it has made in their lives as well! Take a look in our gallery today: What Motivates a Super User? - Power Platform Community (microsoft.com)

March User Group Update: New Groups and Upcoming Events!

  Welcome to this month’s celebration of our Community User Groups and exciting User Group events. We’re thrilled to introduce some brand-new user groups that have recently joined our vibrant community. Plus, we’ve got a lineup of engaging events you won’t want to miss. Let’s jump right in: New User Groups   Sacramento Power Platform GroupANZ Power Platform COE User GroupPower Platform MongoliaPower Platform User Group OmanPower Platform User Group Delta StateMid Michigan Power Platform Upcoming Events  DUG4MFG - Quarterly Meetup - Microsoft Demand PlanningDate: 19 Mar 2024 | 10:30 AM to 12:30 PM Central America Standard TimeDescription: Dive into the world of manufacturing with a focus on Demand Planning. Learn from industry experts and share your insights. Dynamics User Group HoustonDate: 07 Mar 2024 | 11:00 AM to 01:00 PM Central America Standard TimeDescription: Houston, get ready for an immersive session on Dynamics 365 and the Power Platform. Connect with fellow professionals and expand your knowledge. Reading Dynamics 365 & Power Platform User Group (Q1)Date: 05 Mar 2024 | 06:00 PM to 09:00 PM GMT Standard TimeDescription: Join our virtual meetup for insightful discussions, demos, and community updates. Let’s kick off Q1 with a bang! Leaders, Create Your Events!    Leaders of existing User Groups, don’t forget to create your events within the Community platform. By doing so, you’ll enable us to share them in future posts and newsletters. Let’s spread the word and make these gatherings even more impactful! Stay tuned for more updates, inspiring stories, and collaborative opportunities from and for our Community User Groups.   P.S. Have an event or success story to share? Reach out to us – we’d love to feature you!

Top Solution Authors
Top Kudoed Authors
Users online (6,814)