How do I create different views (listings?) from a database?

Support
1

I have been using Ragic for over a year now - and still I feel it does not come even close to meeting my demands.

Now, however, I have decided to give it one last chance to actually get a functioning database.

First, a short describtion of my use case:

I sell seeds and I use Ragic as a product database. My products have A LOT of infornation connected to them. Prices and various calculations, supplier information, products in sales ready stock, products in production stock/queue, links to documentation - you can continue the list.

As I understand it I have one form page for each product, which is fine, but I also only have one listing pages? This is not working at all.

I need several listing pages and some need to be shared with employees. So, for instance, I need a listings page that includes sales the last season, date of expiry, items in sales stock, and a few other fields. This view I use for ordering from suppliers.

I need another view - or another listing - where the fields relevant to my production employees are visible, i.e. information about how seeds are packed, link to print files and so on.

I have tried to work with saved views, but that does not seem to be the way to do things.

I hope my explanation makes sense!

2

Hi David,

Consider each listing page as seperate data base. Ideally a Sale order data base should be different the Inventory data base (means both should have different listing sheets). If thats not the case then column access can be manage though user access for example in entere data sheet some of the column you do not want to show to some specific user.

We are also building a data bases (listing sheets) with the conscept of linking all sheets and restricing user access to all data by user access management. We can discuss futher how we can support each other.

Furher if you have one big sheet and you want to create a different view (different coulmns per view) that is easy and also you can have access restriction per view as well.

3

So, in short, what you are writing is, that Ragic as it is now, is not the right choice for my use?

For us there can be only one database and I fail to see how sales orders and inventory “ideally” should be seperate databases.

4

Sales orders are from customer having sale price per item where as inventory is your own item having pruchase price item. Logcially these should be two seperate tables/sheets/database. (taking lead from other big erp system as well, like oracle sale order has different module where as inventory is differnet etc)

5

So, in short, what you are writing is, that Ragic as it is now, is not the right choice for my use?

I know my company pretty well. We can have only one database. This is the ideal for us. In fact nothing else would make any sense

6

You can make different sheets of the same design and data and have a saved fixed filter. Would that help solve your problem? For instance, in one of ours, we have a sheet for regular staff with a fixed filter of open cases then an admin sheet without the fixed filter that not everyone sees. You set permissions by sheet. You can also turn subtables into their own sheet as well. I hope that helps!

1 Like
7

You can create multiple versions of your product sheet so that you can manage to display different sets of fields for different usages, but still share the data source.

Or if you only want one product sheet, and needs to restrict the field access for different users, you can still do that by configuring the field level access rights.