ContributionsMost RecentMost LikesSolutionsRe: Formula for unique 6 digit number without referencing Record ID #?Ones you have this working properly you can change the key field https://help.quickbase.com/api-guide/setkeyfield.html If you already have relationships working in your app , probably to change now the Key field is not a good idea. In this case make a copy first and see how it works.Re: Formula for unique 6 digit number without referencing Record ID #?We are going to build a Field call [Quote Number] You have a table called "QUOTES" 1) You need to have a parent table I suggest to call it s call it "YEAR" probably you already have it , otherwise you need to create it to get the last number and follow up correlative in the next record. 2) you need to set up in Parent Table of this relationship a Summary Field that calls to the max value of the field we are creating now.[Max Quote Number] This Summery field is in the parent table in this example table called YEAR in this case this field is called [Quote Number], and the new field will call [Max Quote Number] Then you will create another field in the Table QUOTES it is a lookup field and you need to make it fix so we will make another field text snapshot of this one because the [Max Quote Number] will be changing and we want a static number ( this is the key of the successful of this sett up). https://help.quickbase.com/user-assistance/setting_up_snapshot_fields.html Now we have a [Max Quote Number Snapshot] in our Table QUOTE, that gives us the previous number. This is the Field we are building now, and this will be the formula you need to use now in [Quote Number] ; List("", Right(ToText(Year(ToDate( [Date Created]))),2), Right(List("",(("0000")),(ToText(( ToNumber ([Max Quote Number Snapshot])+1)))) ,4)) It works perfectly , I tried it .Re: Formula for unique 6 digit number without referencing Record ID #?First of all you can use this new field as reference # (key) field , the only requirement is that is should be unique, an I understand it is.Re: Formula combining workdates and dates (again...)Hi Mark, thank for being so explicit in your question. It should work I did something identic and it works , you can see any error message. Check that all the fields are Type Date. ([actual finish], [actual finish],[estimated finish], [estimated finish] Re: Import relational data into Quick BaseHi Manish. You do not need to have a previous key in you excel, you can create it if you want. You can set a formula field as a Key field , you only need to use one time this URL in you navigator (X is the Formula Field ID you want to set as a KEY Field(. https://target_domain/db/target_dbid?a=API_SetKeyField&fid=X &ticket=auth_ticket&apptoken=app_token Ihttps://help.quickbase.com/api-guide/setkeyfield.html I use it a lot , I make strings using a formula fields ( using lookup fields o reference fields from parents tables), It works consistently Look this example as you can see the Key field is a formula and it use a lookup field and a reference field to create it , it makes that all work harmonically . I hope it helps.Re: Created a Copy of an Existing App and Want to Use Existing Fields to Link to a New Related TableCan you tell us al little more about your structure and which related field you want to update or keep? I do not get this; "Is there a way to create a relationship to the new assign-the-work app in the existing do-the-work app and have it use the same Related-Team-Member field in the do-the-work app to access the related record in the assign-work appRe: Import relational data into Quick BaseHi Manish, There is a simple way to do it. https://help.quickbase.com/user-assistance/setting_the_key_field.html If you want, you can designate another field in a table as the key field. Of course this must be a field that contains unique values. The advantage to choosing a different field, is that it might contain a value that's more meaningful than an arbitrary number. For example, fields like Part Number, Account Number or Employee ID#, Project Number, Customer ID,.... usually work well. (If you'd prefer, you can make the key field a text type field instead of a numeric field.) When you create your own key field, Quick Base displays it as a required field on the table's entry form. Select in each table the Key filed you want to use in the future, and it lets you to update the data from another external source of data without create new records, because the system detects that the data has already this Key field, so instead of create the new record QB updates the existing ones and only create the new ones if the Key field does not match with the resident records. In my case I am keeping the data continually updated with another database, so all my tables use the Key fields I wanted ( I hardly use the Record ID# it is not meaningful for me), it is easier to make relationships if you know the meaning of each key field. I will tell you my case, for the project Table I select the project number Remember to make this key field Required and Unique in the settings of the Field. If you are not sure , make a copy of you app, change the key in the copy and see how it works before to make it in the real working app. I hope it helps.Re: Quick Base Connected table not updating key fieldYou can see if there is any error ; Re: Summary fields , and override option .Thank you very much Evan, This paragraph is very explicit. If I connect the data to a new table, does it detect the permissions of users in the table where the data come from?. Let\s say, can I allow everybody to see the data in this new table even if the data comes from a restricted table?.Re: i'm looking for an app for manufactured home companyDid you try this? https://knudehansen-5894.quickbase.com/db/main?a=Exchange