DianeSinawi
Qrew Trainee
Joined 3 years ago
User Profile
User Widgets
Contributions
Re: problem populating relationship field from import
Employee ID is not the key field in Targeted User parent table, its Record ID. Since that table is also a parent table in other relationships, if I change the key field to be Employee ID in this relationship, will it automatically change for other relationships, or are they all independent? I don't want to mess up other relationships24Views0likes1Commentproblem populating relationship field from import
In a new QB app we created, we have a table "Phishing Attempts" where we want to create records by importing a spreadsheet. We also have a table "Targeted Users" which has employee info such as Employee ID, email, position, etc. Phishing Attempts table has a relationship with Targeted Users table, where we have the Employee ID field from Targeted Users included in the Phishing Attempts record form along with lookup fields that are automatically pulled from Targeted Users table. The spreadsheet we want to import to create new records in Phishing Attempts table includes an employee ID number. When we import the spreadsheet, we select the target field Employee ID in the Phishing Attempts form. The problem is that the Employee ID field in the Phishing Attempts form is not populating when we do the import. The ID number in the spreadsheet matches exactly what is in Employee ID in Targeted Users table. Is this not working because the Employee ID field in Phishing Attempts is pulling from Targeted Users table? Is there a way to get this to work?81Views0likes4CommentsQuestion about auto-populating fields across tables
I wish to auto-populate a field from another field in another table, but am not sure if it is possible for our specific scenario. If yes, how would I accomplish it? I tried to create an action, but it doesn't work. The affected tables are 'Audit' and 'Scorecard' and I have parent/child and child/parent relationships setup because in each form we need to pull in some fields from the other table. For every Audit record, there will be only 1 associated Scorecard record, and vice versa. Ultimately, we will have multiple different Scorecard tables for different categories. Each Scorecard form will have mostly unique fields. In every Audit record, a Scorecard from only one of the Scorecard tables will be associated, depending on the category selected in the Audit record. I created an action where when a new Audit record is created, then a new Scorecard record is also created, and in the new Scorecard record, the related Audit record # auto-populates along with selected associated lookup fields. This action is working fine. We will create a separate action in the Audit table for every Scorecard table - so when a certain category is selected in a new Audit record, the new Scorecard record will be created in the correct Scorecard table. This action allows us to auto-generate new Scorecard records (instead of manually), and see related Audit record info in the Scorecard record. This action is working fine. But we also need to get the Scorecard record # and some lookup fields into the Audit Record, automatically if possible. I tried creating an action in the Scorecard table, but it is not working, I think because it has no way to know which record in the Audit table is associated with the Scorecard record. Is there a way to accomplish this? Any help is appreciated. Also, I understand we can only have up to 10 actions in one table. So if we needed to have more than 10 Scorecard tables (say up to 50), is there any other way to automatically create new Scorecard records when a new Audit record is created, outside of using an action?55Views0likes3CommentsRe: Can I have 1500 or more fields in one form in one table, spread across multiple pages?
Agreed, it would require too many pages, fields and data, I think performance would really drop. I tested with 12 pages and over 500 fields (total across all pages), and it was already slow without much data in the fields. We've decided to break it up across multiple tables. Thanks for the insight.24Views1like0CommentsRe: How to create form rule to hide pages based on value selected in dropdown fields
I looked at that post and the other post that was linked in that one. But I don't see how those are the same situation as mine. Also there seem to be multiple possible solutions given in those posts, but I don't see one that works for mine. Can you elaborate?22Views0likes0CommentsRe: Can I have 1500 or more fields in one form in one table, spread across multiple pages?
I'll be using the new style form. I've built a few smaller apps in the legacy form, but there were also not as many records in those as there will be for this new app. Wondering if anyone out there has experience with a large number of fields in the new style forms?44Views0likes1CommentCan I have 1500 or more fields in one form in one table, spread across multiple pages?
I will be creating a new app. In one table, is it possible to have a form with around 50 pages, and each page would have anywhere from approx 10 to 50 fields (probably only a few pages would have 30-50 fields, most pages would have 10-20). Therefore, the total number of fields in the form would be anywhere from approx 1,000 to 2,500. Of that total, around 200 fields would be derived fields (formulas). I would also like to have form rules that hide certain pages based on a field selection. NOTE: for each record, only about 60-100 fields would be populated. Are there limits that would prevent me from adding that many fields? Or could so many fields cause performance or other issues, like problems with form rules functioning properly? While it is possible for us to pull out most fields into other tables and connect to the main table using relationships, for our users ease of use and ease of reporting, we are hoping to contain all fields in one form in one table.Solved83Views0likes4CommentsHow to create form rule to hide pages based on value selected in dropdown fields
I have a form with multiple pages. The first page has the main fields, and remaining pages have additional fields. Is it possible to hide or show certain pages based on the value selected in a field on page 1? What I would like to happen: If Service field has value "A" then hide Page 3, Page 4 and Page 5. If Service field has value "B" then hide Page 2, Page 4 and Page 5. If Service Field has value "C" then hide Page 2, Page 3 and Page 5. Etc. or If Service field has value "A" then show only Page 1 and Page 2. If Service field has value "B" then show only Page 1 and Page 3. Etc.27Views0likes2Comments