MarkShnier__YouQrew LegendJoined 6 years ago9027 Posts1259 LikesLikes received283 SolutionsView All Badges
ContributionsMost RecentMost LikesSolutionsRe: Trouble with URL button to copy a record with custom GUID (key) field Unfortunately, the a=GenCopyRecord function does not allow you to specify values for any fields. It simply puts you into the Add record mode with fields copying forward where the field is flagged to copy forward on the field properties settings. But instead, you could use this syntax URLRoot() & "db/" & dbid() & "?act=API_GenAddRecordForm" & "&_fid_6=" & URLEncode([SDO Request GUID]&"-"&ToText([Record ID#])) & "&_fid_7=" & URLEncode([my field in field 7]) & "&_fid_8=" & URLEncode([my field in field 8]) & "&_fid_9=" & URLEncode([my field in field 9]) .. So this is pretty easy to do except that you do have to specify every single field to be copied forward. Re: [Account Manager Email] is Current User I usually do what Mike suggested but your screen shot would probably work if you compared the user field (not the email field) to equal _curuser_ Re: Table to Table Relationships between two apps There are two different approaches you can use here. You haven't really given an example of what specifically you're trying to do, but let's say for example you had a table of customers in one application. You can have a cross relationship where you enter say an order in one application and have a Cross relationship to select a customer and then you would have look up fields to bring down all those lookup fields automatically into your orders table. That does create a dependency between those two apps and a few were in the situation where you have hundreds of thousands of records and a lot of users than you can run into performance issues down the road. The other approach which maintains the apps being separate is you can have what's called the connected sync table. So for example, your source of truth for customers would be in one app and you create a Connected sync table in the other app and then every hour the data quietly mirrors across an updates on its own. So now both apps have a complete customer list but only one is the source of truth and can be updated. Re: Using one field to collect data multiple times. Yes, that is easily done. You trigger the pipeline when the status field changes and copy the value of [Last Modified By] into your tracking field as to who made the last change. You can use the Jinja expression. {{time.now}} to populate the date field or else use the [Date Modified] field to populate your Date/Time of the change field. Re: Using one field to collect data multiple times. The usual way to do this is to build a table which will be a child table to the table trying to track. The pipeline triggers when certain fields are modified on the main table, and you create a new record with a pipeline, remembering to connect to the main table by populating related parent. There is syntax in a pipeline to record both the current value of the field, and the previous value of the field. Would I like to do is to keep the Audit Table very simple and I have a field for the name of the field that was being changed and the old value and the new value. Of course there will be many entries where the old value and the new value is the same depending on how many fields you are trying to track. I filter those off the child Table reports and set up a pipeline to delete those records each night. Re: Numeric Fields Show Separator After 4 Places ... feels like a bug to me. You can report it via the ? icon at the top right of any page in your app. Re: Numeric Fields Show Separator After 4 Places Not sure what to say. Maybe its a bug you need to report. Can I see a screen shot of he field configuation settings? Re: Numeric Fields Show Separator After 4 Places Quickbase defaults to have a numbers up to 9999 show with no comma and when you hit 10,000 it shows the comma. If you want to force number like 9999 to show as 9,999 then you have to change that setting for every field. I assume the reasoning for that behaviour is that it makes the reports a little less wide. I also wish there were some kind of global realm or at least application level default setting for that, but there is not. If you put in a user voice feedback, suggestion, and post a link back here I will vote for it. Re: QuickBase Reports Help I think I need some help understanding your question. For example, when I look in your Screenshot for "Percent exceeding ....... medicare mean and there is a 1 in July 2025, what are you expecting to see there? Re: QuickBase Reports Help Well in the section for configuring the Summary Report for the "Summarize Data" section, it lets you select what to summarize. So select the field(s) that you want to summarize, typically selecting by Totals. You can hover to the right to add more fields to summarize.