Box CSV connected table - unexpected issue
So I was trying out the CSV connected table functionality with Box. As I was getting a feel for how things flowed through my app and testing different fields for the 4 Refresh Key criteria, I went through a few cycles of deleting the records in the connected table, and moving the previously imported CSV files from "Done" back to the main folder for further import testing. [For additional context, this app has a secondary table which uses a Quick Base Action to automatically copy new records from the connected table to the second table based on a another set of filter criteria.] After ~2-3 rounds of the above debugging/testing the process, QB started processing the CSV files as expected - the relevant/expected records were copied from the connected table to the secondary table perfectly, and QB moved the CSV file to the Done folder when complete, BUT the connected table did not display ANY records. I did see as the page was refreshing that QB would briefly flash to the expected record count in the linked table and then ultimately show 0 once the page was fully loaded. What could be causing this? Only thing I can think of is the version control feature in Box still having a deleted version of the import CSV files in one of the QB folders, but that doesn't quite explain it. Please advise ------------------------------ Ken Hillyer ------------------------------
Quickbase connected table view from source table
Is it possible to view from the source table, the tables connected via quickbase connection? I understand when we create a connected table, we can see what table we are connecting to but how would I see what tables are connected from the source app/table? ------------------------------ Asish Mathew ------------------------------
Getting information from one app to talk to another app
I am trying to connect two apps together by creating a new connection. But I can't seem to remember where the APP ID and the Quickbase URL are located. Can someone please help? ------------------------------ Kenisha Terry ------------------------------
Use a Connected Table to populate a Request Table and making those fields non-editable once the Request is saved
Howdy, We keep all of our student employee information in a Personnel application. I am trying to create an application for my hiring managers to submit a request for a merit increase. In the Increase app, I have created an employee table connected to the Personnel table that holds the current information about each employee and their position. The connected employee table has a one to many relationship with the request table. (This allows my hiring managers to just select an employees name when submitting a request and it pulls in all of the current information such as position, position start date, current salary, effective date of current salary). They then fill out the rest of the request with the requested salary, requested effective date, etc. I also need for them to attach a copy of the employee's review. My team then reviews the requests, approves it, submits it into Workday (our University payroll system) and then updates the Personnel app to show that employee's new salary for that position. I've created a couple of checkboxes to show when the request was submitted in Workday and when the employee was updated in the Personnel application. Once complete, the review and request are printed and placed in the employee's personnel file. Unfortunately, the way our workflow works, once my team member has updated the information in the personnel app, when she goes back into the request to check that it's been updated (which effectively removes it from her todo list) and print the request, the request now has the new salary as the current salary (so it looks like nothing has changed). Is there a way to make it so that once a new request is submitted and saved those fields being populated by the connected table are no longer updated? Just making them read only does not do this. The other thing I thought about/tried was creating a "Submitted Request" table with an automation - so essentially when a new request was saved, it copied the values in the Request table over to the Submitted Request table. That way the current salary as of the time of request didn't change. My team member then updated the submitted request with approval, notes, submitted in workday, updated personnel app etc. My challenge with that is in relating whatever document was submitted on the initial request so that it showed up on the submitted request. I want my hiring manager to be able to initiate a request and add a document without having to go back out of that initial request and look up the submitted request. Kind of stuck at the moment, looking for suggestions. Thanks so much in advance for any advice! Below is my current structure for reference... ------------------------------ Andrea Johannes ------------------------------
