Jump to content

telepet

Caspio Ninja
  • Content Count

    73
  • Joined

  • Last visited

  • Days Won

    2

telepet last won the day on June 5 2017

telepet had the most liked content!

About telepet

  • Rank
    Advanced Member

Recent Profile Visitors

1,236 profile views
  1. Thanks @sandy159. I have a hunch a script I have in the header/footer may be the culprit. I will investigate further. In the interim, I've set up rules on the Details page so that Update and Back buttons only appear until users verifies all fields. It's a bandaid fix for this odd behavior. I'll update this thread if I figure out a better solution.
  2. I have a Tabular Report Datapage for which I have enabled editing on its Details page. I would like user to be able to edit a field, click the Update button, and stay on the Details page to continue editing other field if they wish. Currently when Update button is clicked, user is taken back to the Results page of the Tabular Report. I've tried setting Destination after record update to be "Same Form", "Display Message", and "Go to Results Page" but nothing keeps user on the Details page for the same record that's being edited. Any ideas?
  3. Any updates on this? CTRL-F5 and clearing cache may work sometimes but is confusing for our users that are not as computer savvy, and I don't believe that's platform agnostic guidance either. So, any alternative solutions would wonderful to hear. Thanks!
  4. Thanks @Franchiser. I'm wondering-- can you explain why it necessary to uncheck the "Enable HTLM editor" checkbox? I've experimented with having it checked and things still seems to work ok.
  5. Thanks @MayMusic for the information. I've since created a Details datapage that summarize the user input and has two buttons-- one that allows them to go back to the Sincle Record Update page, and another button (labled "Confirm Submission") that actually logs out the user. Depending how this solution works in real life, I may end up using your much simpler solution. Thanks again.
  6. Thanks @Carlson. I'm using a Single Record Update data page, but will explore building out a Details data page, like the one you mentioned above. That said, I wonder on the feasibility of hiding the default "Update" button, then creating another button that is labeled "Submit", but have it be the logout link on the backend. II've hidden a search button before using this code in the header: <style> #searchID { display:none; } </style> ..and so far I seem to be able to hide the Submit button by replacing #searchID with #Mod0EditRecord. Now I think I need to find o
  7. I'm working on a Single Record Update data page. Is it possible to have automatic logout upon hitting the update button?
  8. I'm creating a form with several cascading elements. There will only be one result after the cascading happens. I'd like to retrieve this result but I'd prefer to hide it from the user who is completing the form. Is this possible? Edit: I'm guessing it would be best to simply make a view and then pull any parameters as needed, but it also seems like there might be a way to retrieve results by passing parameters. For the moment I've constructed a view that achieves what I need, but would be grateful if anyone has any suggestions on this front.
  9. Thanks @Vitalikssssss. That link is full of very useful information. I think the JS solution does the trick. Thanks too to @Franchiser. I was able to solve this via CSS as well, using this code provided elsewhere in the forum (link): <style> #searchID { display:none; } </style>
  10. This works perfectly. Thanks @Mathilda.
  11. The above code works wonderfully, and enables a little more flexibility when it comes to layout. I wonder, is it possible to do hide the default "Search" button? I'm attempting to incorporate a search page where there is a "Reset Search" button next to a "Search" button.
  12. Thanks @Franchiser. I'll explore the CSS code a bit. Unfortunately the site is behind a login screen, so I'm unable to share that out.
×
×
  • Create New...