Pixel Wall

So, let me make a slight correction of the problem. The pulldown list in search filter is showing the school name, but the list is sorted based on the order of the occurrence of school_id in the student table.

So, in the example i provided, the occurrence of school_id in the student table is: 1,3,2,4. Then the pull down list will be:

1,Marshall High
3,James Madison High
2,George Washington High
4,Thomas Jefferson High

What I would like to see in the pull down list is a list of school names sorted alphabetically, like:

2,George Washington High
3,James Madison High
1,Marshall High
4,Thomas Jefferson High

Even I create a view for the lookup table and sorted by the school name column, the pulldown list is still ordered by the occurrence of id, not by value.

I don’t have the site publicly accessible. But it’s very easy to reproduce the issue.

Sorry, my organization does not allow me to share anything outside of the organization.

Here is how to reproduce the issue.

You need a table with let’s say 10 fields. In the template, you only select 4 fields to display in list view. If you click “Submit-List”, instead of showing 4 fields as defined in the template, it will try to show all 10 fields all together.

Can you please try again?

I think the problem here is when the data form is presented to a user, there is no user_id info. Which means, I don’t know which user is filling out the form. But the lookup has to return a list of the projects which is related to the current user. So, I don’t have “user_id” to link with, all I have is “$$USER$$” session variable.

In the template relationship view, when a relationship is created, if we have the option to add a where clause to say user_id=$$USER$$, that will solve the problem.

Peter,

When I use “diehard” short code to present a form, and use “Add New” button to create a new record, at the bottom of the form, there are two submit options. One is simply “submit”, the other one is “submit->List”. The simple submit button works well, after you click the submit, it saves the data and returned the data form. However, if you click “Submit->List, it supposed to save the data and return to the list view, however, the list view doesn’t have the template applied to it.

what I have noticed is that if you create two lookup autocomplete relationships with the same table, but referencing different fields, then it will create this issue. Remove either one and just leave one lookup auto-complete linking one key works just fine.

So, let’s say I have the following two tables:

Tasks:
task_id, user_id, project_id, task_name, task_description

Projects:
project_id, user_id, project_name

When a user fills out the task form, I want the user to be able to pull down a list of projects only matching the $$USER$$ variable.

Thanks.

Jay

Very well, so good to hear that. I look forward to the new features.

Not really, in the example from the link, the course_id and student_id are existing column values, but in my case, I need to pass the $$USER$$ variable in the where clause to only retrieve the relevant rows. This will produce the pulldown list only related to the current user.

I personally like the GUI style from the “diehard” shortcode. It’s clean, it’s easy to use. The data form short code apparently is much slower in performance. For the same table, the diehard shortcode can display the list in a matter of second. But the dataform shortcode could take several seconds. It’s a noticeable delay.

The limit option would be so useful in some cases. Please consider it.

Best regards,

Jay

No it doesn’t. I am still experiencing the same issue.

I want to test rolling back to the previous version. But the download link you provided in the earlier reply is for the standard free version. Is there a place I can find the previous release for the premium version? I need version 4.3.1 premium version.

Thanks.

Jay

This happened in Data Project and I used the “diehard” short code for the table insertion to the pages.

I have tested on all my tables, they have the same issue.

Thanks for the link, I will see if I can roll back.

Jay

I am talking about the front page. Most of our page use diahard shortcode to insert data table. So, it will be nice if we can hyperlink a column in a table and jump to the view page of that record.

Peter,

I read the hyperlinks section of the document, however, the example you have shows this feature will create additional column you need to have a URL where you can insert the $$id$$. This is different from the hyper link I was thinking about.

In my case, I want to just underline the name that’s linked to the foreign key, and when user click, it will bring to the view page of that record.

The document doesn’t show how to reference to the view page of a data element.

If I may, I had similar issue before. The way how I fixed it is to rename some of the database column to a more unique name.

What I have noticed is that if your database have two tables share the same column name, that’s when it will cause 403 error. For example, your contact table and company table both have a column called “name”, then most likely, you will get 403 error. To fix it, you just have to rename to book_name, and company_name.

Not sure if you have the same issue, but that’s how I fixed my issue. Since then, I always name the database column using specific unique column name. However, I have also noticed that having the same “id” column throughout all your tables is not a problem.

Hope this helps.

Jay