Hey Mark,
I thought more about what you said and, before I went into redesign, I managed to get the report link field to populate using the key. Unfortunately, other lookup fields to yet another table are based on an email address field. Those fields don't normally populate until the email address is entered and then the field "clicking" out of the field to let things calculate. Using the formula URL, those fields do not populate until after I choose to edit the newly added record. Any suggestions for how to handle that? Do I need to redesign anything?
Immediately after I posted this, I thought about what the problem likely is. Dynamic form rules. I had an issue with the lookup working due to case sensitivity so, I have a hidden field that picks up the LCase of the email address. The lookup is done based on that field, which can't be edited. Dynamic form rules are in driven by the email address and the hidden email address fields for setting what sections are visible as well as setting couple of checkboxes. Will the URL not work because of the Dynamic form rules? Is there another API call I can make that will trigger the form rules after the record is added? I am looking to avoid having the record shown while being edited, if possible.
Qrew LegendSorry, but I'm not understanding the question.
I gather you're using an API to actually create a record so you were using the API of API_AddRecord
When you view that record the form rules would all activate in terms of show/hide, if you're expecting any formulas to edit the record then they will not fire until the form is put into edit mode. If you wanted any other fields to be populated to replicate what the form rules do then that would have to be built into the API_AddRecord. You can populate an unlimited # of fields with the one API. But, like I said I really am not understanding your question, this response may not help you!
Sorry. So, you ended up answering my question, believe it or not. Lol. Unfortunately, I misunderstood my situation so, let me try again. I have lookup fields in the form. Some of them are for one related table and the rest for a 2nd related table. When I make the API_AddRecord call, only the lookup fields for one table is being populated. The other fields are blank. I do have the key for both related tables being populated with the API call so, I don't understand why the fields for one table are coming up blank. When I go into edit mode, they immediate populate so, I know the correct key is being added with the API call. Any input regarding that would be greatly appreciated.
James
Qrew LegendThat seems impossible. Can you show me the code for your API_AddRecord?
Okay. I am back to the dynamic form rule being the issue. While I am using the right value for the lookup fields in question to populate, because of case sensitivity with the email address, I have a dynamic form rule populating the field that is driving the lookup. Will dynamic form rules not change the value of fields until the record is in edit mode or is there a way to make it happen?
Qrew LegendDynamic form rules only kick in when a human user with hands on the keyboard puts a record into edit mode. If you want something to happen without putting the record into edit mode then either your API has to do that when is the record is created or you have to trigger a Pipeline to do that editing for you.
Here is the URL I am using to make the API call. It works without error but, again, not everything is populating. https://builderprogram-jcarr.quickbase.com/db/bqjts5s7z?a=API_AddRecord&_fid_175=yes&_fid_45=audreywright1@gmail.com&_fid_174=yes&_fid_10=389&_fid_161=yes&apptoken=c7e8rngbcix5bscgwyxitde55c57
------------------------------
James Carr
------------------------------
