ContributionsMost RecentMost LikesSolutionsIs it possible to open File Attachment permissions to all users in Realm?I have multiple apps for different departments within our organization, and all of our customers are viewable through sync tables with a central app storing the source data. I have another table holding anywhere from 5-20 File Attachments per customeras individual records, and logging data tied to the file attachments. This table is also synced to each app. Any app can upload file attachments to the source Files table by adding a record to a hidden table within their own app which then posts a copy of that record to our source table through an API_EditRecord webhook, which then updates the connected table in their own app. They do not realize the hidden table even exists.The goal is that our end-users only appear to interact with the sync table in their related app for simplicity of use, however, they are really funneling data through the central app. I have a button linked to the file on each record, and a user can download the file by clicking this button. This looks like the following:https://drive.google.com/file/d/1gLZOyzZjV3euCiVY2FEF0A70ZplgIaVr/view?usp=sharing The problem is that this only works for users with roles in the central app. All of the other users in our realm cannot download through the link, as they don't have access to that app. I see that I'm able to open file attachment permissions to anyone without a login, but we are storing company-sensitive information that I do not want to open permissions for. I would like to open permissions for anyone in our realm to download file attachments from the Files table in our central app. Is this possible? Re: Connected Tables vs. Cross-App Relationships vs. AutomationsThe tasks are staying connected, I have a dedicated customer ID that's drug around with them. The problem is that the data in the fields is disappearing, and I just have to open the "Edit Form" screen to get it to re-appear. I don't actually have to make any changes, or edit relationships. When the Sync table refreshes, all of the lookup fields that rely on it are blanked until I go into the form's edit page. Re: Connected Tables vs. Cross-App Relationships vs. AutomationsThank you! I have been extremely diligent in the transition to avoid taking any action in an app that will require processing from another. To this point, I haven't made a single cross-app relationship or automation. Our new set of apps are not connected to the old one in any way, I have pulled the data into the new apps using table-to-table field imports that are set to only run manually. With our main focus being performance, I've kept in mind your exact sentiment. If our apps do become reliant, then not only have I still brought back every performance issue, but now I also have our data segregated, creating the worst of both worlds. You have confirmed by suspicion and I will avoid cross-app relationships altogether. That being said, my thought regarding sync tables versus automations is that it's simply an assessment of when it would be best to pull data versus push data. Can you think of anything else to keep in mind while building them? Also, I have noticed an issue in some of our first few tests that I haven't been able to fully diagnose yet. I have a sync table in a department app for Customers. In that app I have a Customers to Tasks relationship. The lookup fields in Tasks seem to clear themselves every time the Customers table syncs. However, when I preview the form I am viewing them on, all of the data on every record appears again. This is very strange and I'm not sure how many different actions allow the field data to re-appear yet, but I'm wondering if this is something you've seen before? (Maybe this warrants it's own post) Connected Tables vs. Cross-App Relationships vs. AutomationsMy company is currently building out a new set of apps to transition into over the next 30 days. We've been running in the same application for roughly 6 years, and it has been great to us, but it has also been a learning process. After some research, we've decided to transition to a multi-app setup to address security concerns with many of our third-party vendors, and to address the performance issues we've seen by having an excessive amount of formula fields and relationships in one app. We have separated our apps by corporate department and are in the table-building stages currently. We have one central app dedicated to company-wide reporting and central data management for the important stuff, and five department apps for day-to-day processes. I have seen a lot of conversation around connected tables and cross-app relationships here, but I'm wondering if Automations may be a more useful solution to some of our problems. Right now, all of the department apps have connected tables pulling our Customers, Employees, and Companies from our central app. From there, each app has it's own tables for that teams needs (We are a contractor, so we have Inventory and appointment management in one, processing tasks and jurisdiction info in another, accounting data in another, etc). From there, each app will be sending data back to our central app for reporting purposes (how long it takes to complete tasks, big-picture accounting data, etc). I'm having trouble identifying when to use a connected table to send the info, when to lookup the info in a relationship, and when to use an automation to update the info across apps. I'm thinking we're likely going to use a combination of all 3, but I don't have a complete enough understanding of them to properly identify what will be best in each situation. My only thought walking into it is that we will likely avoid relationships, because I suspect that will put us in the same performance issue we've been having in a single app. However, I also believe that intelligent structure design will solve this problem. Long story short, what are the pros and cons of Connected Tables, Cross-App Relationships, and Automations in multi-app data transfer so that I can better design the foundation of our apps? I understand that this is a huge question, so thank you in advance.Help with API Data Imports - Updating Existing FieldsI work at a solar company, and I'm trying to utilize the API of the NREL's PVWatts tool (https://developer.nrel.gov/docs/solar/pvwatts/v6/). I have written a URL field that will create the HTML link with all of the inputs already entered. This uses other fields on the table that are filled out by the user. What I would like to do is utilize the data returned to update different fields on the same record. An example report of what's being returned can be found here:https://developer.nrel.gov/api/pvwatts/v6.xml?api_key=DEMO_KEY&address=1600%20Ampitheater%20Park... I would like the 12 numbers returned under the "ac-monthly" section of data to update 12 fields on the same record with those numbers. Here is a glimpse of the page I'm working with: https://drive.google.com/file/d/1kFFJEQGp_Fq0-wrsvWByCe7izyNPfP_U/view?usp=sharing The goal is that the user will put in the array data, press the button, and the output of that array will be placed into the A1 Jan - A1 Dec fields. Sorry if this concept is already on the forums somewhere, but I've been searching for a few hours and everything I find seems to related to using the Quickbase API, not having Quickbase use other APIs. Update: The PVWatts API can return XML or JSON data, if one would be easier to accomplish this than the other.