Ed727

Thank you for taking a look. I've tried the grouping and pivot table features -- they provide a fix in terms of organizing all the results by distinct results, however they still list each result as part of the grouping. And all of the data I also need to show (event location, date, etc.) show up in the sublist of the duplicates, not on the main line. This approach would work OK when each result is meaningful in and of itself (for example invoices), but in a use case of subject tags it's not OK. I've asked around a lot and I think that unfortunately this is not an area Caspio can handle without some extensive custom coding which can be tricky even for outside developers. From doing some research, it appears that other platforms handle this by allowing users to directly create many-to-many relationships between tables, and the platform deals with the linking table in the background. Perhaps this will be something Caspio will address down the road, either directly or through expanding the functionality of the List datatype.

JJMcM123 - I am curious how you resolved this. I would have tried to avoid this issue by having the datapage search only the Products table (where each product is listed only once), and in the Product table you connect each product to only the most recent price. If you want the ability to show historical prices then that's when you'd go to the Price table, for example to produce a list of prices per Product.

I can't figure out how to search based on many-to-many relationships without getting duplicate results. To create a many-to-many relationship in Caspio, you have to use a joining table which connects the two other tables. Each of the other tables connects to the joining table via a one-to-many relationship. Here's an example of the issue below, based on an Events (i.e. conferences) database that uses Subject Tags. I have an Events table (list of conferences) and a Subject table (list of Subject Tags). Each Event will have multiple Subject Tags assigned to it. I create a joining table, and each entry in the joining table consists of an Event and one of its Subject Tags. Therefore each Event is listed multiple times, once for each Subject Tag. An example table and relationship are below: To allow a user to search for an Event based on Subject Tags, I then create a view based on the joining table. The view pulls in all the other information for the Event (location, date, size, etc.). The search form for the user then refers to that view. However, problems arise: 1) Since each Event is listed multiple times in the joining table & view (once for each Subject Tag it has), I can't list all the Events, or all the Events filtered by something other than a subject tag, because an Event will show up multiple times. 2) I can't allow the user to search for Events using multiple Subject Tags, because if the Event has those same multiple subject tags, it will show up multiple times in the results. 3) If I use any other many-to-many relationships for Events, I need to create a separate joining table, view and search page. Thus I can't offer the user a unified searching experience. I've searched all over for an answer to this issue without any luck.

I haven't used Wix but have been using Weebly and use parameters extensively. So far so good in terms of deployment. (Separately, Weebly seems to be limited how it allows you to build and style pages, but perhaps professional web developers know ways around that). One thing to be aware of regarding styling. When you embed Caspio within Weebly, the styling on the datapages is the style you set in Caspio... unless that data page or field is something you've built in .html, in which case the styling picks up the css styling from Weebly. If you are using html pages or fields, build in extra time to fiddle with the styling to get it all to conform. It took me some serious time to understand where the styling was coming from and to get things to look decent. This discrepancy wasn't in the Caspio documentation so it took me by surprise and I had to experiment with the styling to understand where it was coming from and what controlled it.

NickO -- I am curious if your issue is the same one I am describing in this post -- that if you search a joining table used to create many-to-many relationships, you get duplicate results. I am still searching for a solution to this issue but no one seems to have one.

I am having problems with this many-to-many area as well. The tutorial mentioned here and the documentation don't address it. Yes you can create a joining table to form the many to many relationships. But all sorts of problems arise, and I haven't as of yet found any solutions. The main problem arises from the fact that a Caspio form (or "datapage") is tied to only 1 specific table or view. And therefore if you're searching based on a many-to-many relationship, your search form is then tied to the view that has been created off the many-to-many joining table. Using the example mentioned above, a table of businesses which are connected to a table of subject tags: 1) If you want your user to be able to search or filter based on multiple subject tags, they'll get duplicate results, since some of the business may contain the multiple subject tags. That's because the search form is searching a view which is based on the many-to-many joining table. You also clearly couldn't "display all" on that page, since there would be tons of duplicates. 2) If you have multiple many-to-many relationships for a dataset, then that means multiple joining tables, and multiple search forms. You can't create unified search functionality. The user would have to go to a different search form for each many-to-many relationship. There are some other problems as well: 1) When entering data, you'd need to create a separate entry forms each type of many to many relationship. So, if your business has 2 many to many relationships, then that's 3 entry forms total (1 to create the business; 1 to create the first many to many relationship; 2 to create the second many to many relationship). 2) To display the many to many fields for the business (for example you'll want to list the subject tags when you show the business details), you need to embed them as an iFrame. Then it takes some work to fiddle with the formatting to make everything look consistent. It would be great if I'm missing something here, since that would allow me to overcome hurdles I'm facing with many-to-many.

That's fantastic, thank you! I dropped the code into the footer and I also decreased the timing from 5000 to 500 to reduce the delay before it ran; and it runs great!

Hello, checking again to see if anyone might have a solution, before I table this as not possible. Thank you.

Hello - I have a search form and a results list on the same page, per this approach: https://howto.caspio.com/tech-tips-and-articles/tech-parameters/add-a-search-interface-to-results-sets-page/ The search form is a submission form which passes parameters to a results list. Both are embedded in the same web page. When the web page loads I'd like the search form to auto-submit based on some default values, so that a list of results is generated. Otherwise it just shows "No records found" until the user submits the form. I see Caspio provided an auto-submit javascript solution below. However, since the submission form reloads after each search, the below creates an infinite loop. Does anyone have a simple solution so that the search form auto-submits ONLY when the user first visits the web page? Thank you.

Hello -- hoping for some upfront guidance on how to create a login process that matches what many sites are using these days, like a news website. The process and functionality is... 1) Visitor navigates to a Content Page that is visible to anyone, let's say a page of news headline links. 2) There is a Login Link on the top right of the page. 3) A Registered User can click on the Login Link and: a) They will be taken to a page or pop-up where they can log in. b) After logging in, they may see a customer welcome message or notice from the website. c) They can click a link to return to the Content Page. d) On the Content Page, instead of displaying a Login Link top right, it now has links for the user -- like Logout, Account, etc. d) They can click on news headlines and view the articles. 4) IF a visitor arrives at the Content Page and clicks on a news headline before they login: a) They will be redirected to a login page or pop-up, as described in #3 above b) However, after logging in, instead of being directed back to the Content Page, they will be directed to the news article they clicked on. I know I could take care of #1-3 by duplicating the Content Page -- one version for a visitor who is not logged in, and another for a visitor who is logged in. But that seems like a clumsy way to do it since I would need to keep two content pages identical and updated. And that does not address #4, where someone clicks on a news headline, is redirected to a login page, and then expects to proceed to the news article rather than being redirected back to the Content Page and having to click on the desired content again. Thank you.

Thank you, that was what I was afraid of, but I'm glad to have the clarity and do the manual fix now and set it up correctly going forward. This would be a good area for Caspio to build into its documentation.

Another way to try it... If you didn't want the first form to actually make a submission to your table, you could set up that first form as virtual fields an then pass the entries to the second form as parameters. The second form would then receive those parameters and enter them into the actual entry fields, which you'd hide (since the user has already "entered" them in the first form). When the user fills out the new fields he/she sees in the second form, the entries for both the first and second form are then entered into your data table in one go. To enable a user to go back to the first form prior to submitting the second form, create the back button as an actual link back to the first form, (or try the back button javascript) and set up the first form to also receive parameters so that it "catches" the same parameters it sent to the second form. This then pre-populates the fields in the first form with the info the user already put in. One complication is ensuring that that you don't run into a situation where old parameters are sitting around and appearing in the first form's field uninvited. You can use the ?cbResetParam=1 when first directing the user to the first form, which will clear any parameters before the user sees the form. However, if you do this, the link from the second form to the first form will need to be a url link that doesn't have this parameter clearing instruction. If you use the javascript "back" button, it's the same as hitting the browser back button and the first form page url will still have the ?cbResetParam=1 which will clear the entries. I have not tested this approach for your use, but I've used a similar setup for another purpose.

Hello -- hoping someone can clarify whether an issue related to line breaks is fixable or not. I've searched the documentation and forum for an answer without any luck. I have a Text(64000) data field in my table which I use to store multi-line addresses. Street is on the first line, and city/state/zip on the second line. In a datapage entry form, using text area w/out rich text editing enabled, I can put the street and city/state/zip on different lines within the field by hitting return. Since I'm not using the rich text option which puts in html behind the scenes, there is no <br /> separating the lines. When I look at the data table itself, the lines are broken correctly in the field, and there isn't any html. (I assume Caspio has some way of recognizing the line break.) I can also create these line breaks when entering the address directly into the data table, by using Alt + Enter, as discussed in these release notes: https://howto.caspio.com/release-notes/caspio-bridge-9-0/ The field is called "Address". When displaying the Address field on a datapage details page, if I select the field directly as a field for display, it displays the two address lines correctly, like the below: 24 Willie Mays Plaza San Francisco, CA 94107 However, I've built my datapage details page using html blocks, given that the standard formatting options from direct insert aren't enough for what I need. So I insert the [@field:Address] into that block, but now it doesn't recognize the line break, and displays like the below. 24 Willie Mays Plaza San Francisco, CA 94107 I know I could go in and enable the rich text editor and insert <br /> where needed and then output the [@field:Address] in the html block as html rather than a string. However, I have nearly 1,000 addresses and manually going in and creating the breaks will be a major pain. Before I go through that process, I wanted to check that I'm not missing anything. Thank you.

Thank you very much!

Hello - I'm trying to find the easiest way to remove the scrollbar from a listbox on a submission form. For example, in the following screenshot I've set the listbox with enough rows to cover all the options. The scrollbar still appears however.