I have a merchant application form that I want to split up into multiple regions so that the user only has to see one section of the application at a time. Each region is tied to the same table therefore:
Each region would have to share the same primary key
I only want one submission of the form items at the end of the form
I read this post Create an Apex form with multiple pages
which makes it seem like an easy to do process by using the Hide and Show Region template and manually separate the form into multiple regions. The problem I'm running into is that Apex requires a primary key to be tied to each form region, but you also can not have duplicate items on the same page. Any ideas?
-- attaching the PNG of the error message here Primary Key ERR
To me, it looks like a single page with several regions. Doing so, you'd have only one primary key item.
Logically, you'd separate items into different regions. Each of them should use its "Server side condition" which would decide whether to render (i.e. display) that region at certain time or not. It means that it doesn't have to be a hide and show region (besides, it is always here and visible, user just decides whether to reveal its contents or not). You'd create any region type (even an ordinary HTML region).
For example:
the first region displays customer ID, name and address. Other regions are "hidden" because e.g. P1_ID IS NULL is met as no data has been submitted yet. Once user enters ID, name and address and submits the page, P1_ID gets its value which enables other region(s) to be displayed
the second region contains items about some other customer's data; it is now visible because P1_ID is no longer NULL, but 3rd region is still hidden as you didn't enter some required data in the 2nd region which would let the 3rd region to be displayed.
and so forth
Note that the post you are referring to is 6 years old. That is like medieval in apex terms - so much has changed since then.
This is a way to do it if you want multiple pages. Just create multiple pages with the same form (using the create form functionality) and depending on the functionality needed on a specific page you delete the page items you don't want to show. If a database column is not included in the form it will not be touched by the dml process. This should be relatively simple to create.
Note: if you want to get up to speed on forms, read this blog
Related
I am developing a Power App using the Teams version. We have two tables in Dataverse acting as the main data sources. There is an inheritance relationship between these two tables, where one holds parent objects and the other child. I have an overview screen which displays a single record and it is important that a user can select both parent and child records from a single combobox and have the data associated to the selected record displayed.
In order to achieve this I have a collection which holds the ID and Parent/Child type of each record to form a full list of records from both tables. Collection is built as follows:
ClearCollect(Collection_RecordSelect,AddColumns(ShowColumns(record_parents,"recordID","recordID_numeric"),"type","parent")); Collect(Collection_RecordSelect, AddColumns(ShowColumns(record_children,"recordID","recordID_numeric"),"type","child"));
When a user selects a record from the combobox, the ID value from the collection is looked up against the respective data source to get the rest of the data for the record.
The issue I have now is, when a user makes a change to a record in another screen, the app returns to this overview screen to show the record they have just changed. To achieve this I used the DefaultSelectedItems property of the combobox which looks at a selectedRecord variable containing the record ID as a string, set after a user changes the record in another screen. As the combobox requires a record, the combobox uses the selectedRecord variable to Lookup into the collection I referenced earlier to get the full record, unless it's blank in which case it default to the first record. Shown below:
If(IsBlank(selectedRecordID),First(Collection_RecordSelect),Lookup(Collection_RecordSelect, recordID = selectedRecordID))
This results in the combobox displaying two instances of the selected record and showing the old version of the record before the user made changes on the overview screen. If you select another record, the duplicate disappears. If you select the other duplicate record in the combobox, the user's changes are then shown on the overview screen.
Screenshot of duplicate record in combobox.
I have tried creating a single collection, containing all records from both tables, however as they are slightly different due to the inheritance field in the child table they don't merge properly and data is missed. Unfortunately, I need the inheritance field on the overview screen so I can't use ShowColumns and remove it.
I have recently re-built the app in Teams as opposed to standard Power Apps. This solution worked fine in the standard Power Apps environment, so I have a suspicion it may be a bug with the Power Apps for Teams combobox? Unless I am making a mistake, I think this is probably true as I've just tested and the "Classic Control" combobox doesn't have the same behavior, shame because it looks rubbish compared to the Teams one!
I have turned off multi-select on the combobox and search and the problem still exists.
Any help would be hugely appreciated!
I have a scenario where I must show the user four combo boxes. Each combo box has a list of system users. There are some roles in the system, but there are four important ones, and that's why we have four combos. Each combo box is already filtered by role id for the system users. The four combo boxes do not depend on each other (no cascading).
Here is the UI hierarchy:
Ultimately, I require the List<ApproverUser> to receive modified when this whole thing is submitted. The form element sits in the first EditorTemplate: LetterEditor.
Plan:
For the UI, at least, I see myself
running a loop for all roles ordered by role sequence
render a combo box and load data passing the role id to get filtered system users
Now, the user should be able to pick each approver in the four combos, and also, if in the future, the approvers increase, I won't be hard-coded to four combos only.
The issue I foresee is how this will correctly map back to the List<ApproverUser> on the model.
Any guidance is appreciated.
I have an Access app I wrote, to handle the data work a team needs to do, rather than working on a giant excel spreadsheet. The one annoying constraint is people are sharing this db over a wifi connection.
I have the db split, so users get a copy of the front end in runtime, when they run a bat file shortcut. The backend is on a hard drive, connected to a laptop, which is directly connected to the wifi router.
In this app, I have a form with a combo and some buttons to perform functions on dynamic queries, so the user can filter the records. Everything is in 1 table, and the table has about 75,000 records. When the users go to the form, on load, a sql string is constructed, to set the base recordsource for the form.
When a user clicks any column in the datasheet view subform object, the whole form freezes and you can see in the bottom right Access says "running query". The users like to click the drop down arrow by the column to filter based on values, and that usually isn't too bad, but clicking on the column seems to trigger a query to run and I don't know why. Can anyone help?
I just want to up the performance on this application as much as possible. These forms allow the users to filter to a set, select the rows they want, click a button, and a column gets tagged (assigning those records to someone). Then a button shows, they click it, and those results are exported to an excel formatted template. They send that to the person assigned the records. Later that comes back to us, and I have a button for our users to import that sheet and process what the assigned person entered on their records.
Thanks for any help anyone can give!
I want to use JMeter to do load testsing.
I will use the requests to simulate user behavior on my website.
Depending on what a user is filling out on the page, new fields may appear and these must be filled out.
For example if a user chooses a value in a dropdown box, depending on this value can appear below the text fields and / or the radio button group, etc. it is quite unpredictable so the possibilities are wide.
That's why I made a little program with Selenium to build a dataset based on what the application presents to me as fields.
So I can not present a CSV with a quantity of fixed columns since this one is dynamic according to the different choices of the users.
How would you have implemented this?
I am currently working on a project in ServiceNow that requires me to configure around 500 descendants of the Configuration Item table by adding multiple form sections to the CI's with around 10-20 fields in each of these form sections. I currently am doing this by going into the Form Design for each CI, and manually adding these form section and fields for every CI individually, which takes far to long to do for 500 CI's.
Is there a way to add a form section to multiple CI's without having to go into the form design on every CI you want to change and adding it manually?
Technical answer: yes, because all of that form layout data is stored in tables (sys_ui_form_section, sys_ui_section, sys_ui_element, etc) that you could script to insert relevant records. However, due to the complexity (form sections, form elements, ordering) and the potential to run into conflicts (forms differ between tables), I would recommend this only as a last resort.
I think the real question is why is it required to have all of those fields displayed on the forms? If you're populating data from Discovery or a large import, can those fields just be visible by a list page, or just be available to use in filters? Will users actually be clicking to view a CI record and need to see that data on the form? The other part to consider is which view you are adding all of these form sections and fields to. As an example, a user won't see the data on a reference field hover if you're only making changes to the Default view, and won't see any of the fields on a mobile device if you don't add to the Mobile view.