ContributionsMost RecentMost LikesSolutionsRe: what coding language should i learn to work with quickbase API and pages?I recommend JavaScript because it is native to a browser and you can embed the JS code in a page and host it right on QuickBase (under pages). But you could use other languages such as Ruby (on Rails), Angular, Java, Python, .NET (C# or VB.NET) as well. It all depends on what you are trying to do. If you are trying to develop a separate application using any of these languages, you could use the API calls within those languages but if you are just trying to get a simple task with minimal infrastructure and want to host it on QuickBase itself, JavaScript is the way to go. ------------------------------ Surya V Avantsa ------------------------------ Re: Can I Use a "Page" as a Table Home Page instead of a "Report"?Create a field of richtext type in that table. Then Create another field of boolean type. Let's say home page. Now add your html content for that page in that column and mark the boolean field true. Create a report with that Rich text field where home page is true. Set that report as your home page. You get the idea? Mark used to teach us these tricks. But if he says it's not possible, may be QuickBase has changed so much? ------------------------------ Surya V Avantsa ------------------------------ Re: Roles and permissions I know it is supported. I've built an employee table with supervisor info using self joins. It works like a charm. Most people at QuickBase technical support don't know enough about QuickBase. BTW, I solved the issue as follows. I have added a user list field that starts with the record owner on the organization table. That user and anyone else that is added manually to that field will have access to it and all its child table. This works. This is completely top down and never going going bottom up. -- Thank you, Surya Avantsa Re: Roles and permissions QuickBase support gave up and pointed me to the forum. At one point, the QuickBase support lady said that creating a self join is an error and is not supported by QuickBase. -- Thank you, Surya Avantsa Re: Roles and permissionsBlake, There is no misunderstanding. You are absolutely right with that design. That is exactly what I have too. Still, I have the same issue. The other thing I noticed is, these permissions work right after I save the formula or the permissions. Once I am happy that it works, if I just refresh, it stops working. Then if I open the formula and save it and try again, it works. I refresh, and it stops working. I think this is a bug. ------------------------------ Surya V Avantsa ------------------------------ Re: Roles and permissionsBlake, Since Organization is the grandparent of Employee, in the Organization has Employees relationship, Organization would be a lookup field. And QuickBase does not allow you to create summary fields based on a lookup field. ------------------------------ Surya V Avantsa ------------------------------ Re: Roles and permissionsMark, what I want is the other way around. Organizations where OrgType is Vendor are parents to Organizations where OrgType is Customer. I am able to restrict the view to the Parent (Vendor) Organizations correctly. Based on this, I am trying to restrict access to its Child Organizations (Customers). This is the part that is not working. ------------------------------ Surya V Avantsa ------------------------------ Re: Roles and permissionsOrganizations have Departments Departments have Employees Lastly, Organizations have Organizations With the permission set up done thus far, I am able to successfully hide organizations that a person does not belong to. But I need to be able to show them their organization's customers (which are also organizations). ------------------------------ Surya V Avantsa ------------------------------ Re: Roles and permissions ------------------------------ Surya V Avantsa ------------------------------ Roles and permissionsFolks, I have a permissions question. My use case is as follows: Organizations have Organizations. The parent organization is a Vendor and the child organization is their customers. Organizations have departments and departments have employees. I want those who are in the HR role to be able to view their Parent organizations (Vendor) and the customer organizations. They should not be able to view other organizations or their customers. Each person in the HR role is an employee in their respective "Vendor" organization. (Organization table has a type field: Vendor or Customer) The Employee table has an email address as the primary key and a formula user field based on that email address. Now, I have a formula field "This is Me" to be true when the current user is the User field on that employee record. Then I have a summary field "# of Employees Who is Me", on the "department has employees" relationship that is defined as the count of the rows where "This is Me" is checked. This rolls up to the Organizations table on the Organization has Department relationship as "# of My Departments". To control the view of the organizations that are the customers of my vendor organization, I have Orgs has Orgs relationship where the reference field is the Vendor Organization. To be able to decide which Customer organizations an employee can view, I have pulled down the "# of my Departments" as a lookup on this relationship so the Organization table how has "Vendor Organization - # of My Departments" Now, to set the permissions of what organizations an HR role person can view, I have set it up as "# of My Departments" > 0 or "Vendor Organization - # of My Departments" > 0. The issue is: When I test as one of the Employees of an organization who is in the HR role, I can see my Vendor organization but not its Customers Organizations (which are the child records of the Organizations table) What am I doing wrong? Or how else can I accomplish this? ------------------------------ Surya V Avantsa ------------------------------