Hey,
I'm running into a problem of designing a simple power app that helps create price list items (default Dynamics 365 table). The Dynamics 365 sales environment is not great for this and it was requested to have a separate power app for adding existing products to a price list (which is a price list item).
Not very special if you look at the Dynamics form so I started out rebuilding it, but I ran into problems with required fields. I understand them, but I don't understand why some fields are not required in Dynamics, but are in Powerapps while it's the same required dataverse field. I'm specifically referring to the 'rounding policy, option percentage' fields. They are locked and not required on the Dynamics default form as shown below:
I thought they might be automatically populated by some backend script, but if I look at the dataverse table they seem really empty:
However, in my powerapps form it fails to submit without these fields / a value. I tried using 'blank()', but that does not work either. We do not use any of these options and my powerapps form now becomes I mess because I have to add all these fields, set some kind of default value and hide them. Is there another way to deal with this? Am I overlooking something?
Thank you very much!
