I will give you a concept to think about, but it has its dangers of false positives and difficulties handling errors (so it is not something I am recommending), but if your Lookup picked up the ID of the latest bid and wrote that to a number field in the new record, you could set that field in SharePoint as requiring unique values, the second one would fail at a SharePoint level (as I mentioned you would then have to try and handle this error and provide a message). The best you can do with reliable means is a lookup before patching. The exact timing here depends on bandwidth / app performance and may be a few seconds. Item_Name: quickbidselected.'Item you go back to my first post, you cannot prevent absolute "concurrent" conflicting bids. 'Name (Title)': Office365Users.UserProfile(User().Email).DisplayName,ĭesignation: Office365Users.UserProfile(User().Email).JobTitle,ĭivision: Office365Users.UserProfile(User().Email).Department, May i know how to prevent this? This is the below code when user submits the bid successfully. When i access User A screen and User B screen after bidding, below screenshot is being shown which is wrong. ![]() ![]() When two users access the app at the same time and bid for items, two winning bids are being created which is logically wrong. The app landing page has a gallery which looks like below where user can bid for items. Hi have a bidding powerapp with SharePoint as the datasource.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |