Jump to content
Oyseka

Input clash on multiple devices. design help please

Recommended Posts

Hi All, I am developing a system to produce, among other things, Quotations and Job Cards in a mixed FMP and iOS environment. One to the problems was the lack of support for autocomplete of drop down lists in iOS which I have tried to get round, with the help of this community, by using a filter from a cartesian join relationship. I now find that when more than one person is creating a quote on a mobile device from the hosted file that you may end up with other peoples input in your QuoteItems table for the quote you were creating. Can any one tell me how to change the relationship ,(design), to stop this.

On a desktop system the flow is:

From the Customer - create Quote - Quotation Table

In the Quotation Table use the portal into QuoteItems to select the Department, Product and Quantity

Screen Shot 2017-02-26 at 19.58.26.png

Share this post


Link to post
Share on other sites

I don't think we have enough information.  The user is on what layout that is based on what TO?

 

Why do you have the fields circled when they don't play a role in the Quotations to QuoteItems relationship?  I'm assuming that the portal you are talking about is one that is on a layout based on the Quotations TO and that the portal uses the "QuoteItems" TO?

Share this post


Link to post
Share on other sites

Sorry Wim, I neglected to include the iOS flow. The filtering of both the Product and Department takes place in fields on the Quotations table for iOS, which is where I think the problem stems from. When a filtered selection is made it is then moved to the QuoteItems table. This is the script that is used to select the Product and after Product input takes the user to the Department selection field

Set Variable [ $QuoteId; Value:Quotations::__QuoteId ]

Set Variable [ $ProdName; Value:Prod_QuoteAll::ProdName ]

Go to Layout [ “dLayQuoteItems” (QuoteItems) ]

New Record/Request

Set Field [ QuoteItems::_QuoteId; $QuoteId ]

Set Field [ QuoteItems::ProdName; $ProdName ]

Commit Records/Requests

[ No dialog ]

Set Variable [ $$QuoteItemId; Value:QuoteItems::__QuoteItemId ]

Go to Layout [ “iLayQuote” (Quotations) ]

Set Field [ Quotations::gProdFilter; "" ]

Go to Layout [ “iLayQuoteDeptSelect” (Quotations) ]

Go to Object [ Object Name: "FilterDepartments" ]

Go to Field [ Quotations::gDeptFilter ] [ Select/perform ] 

Share this post


Link to post
Share on other sites
4 hours ago, Oyseka said:

Sorry Wim, I neglected to include the iOS flow. The filtering of both the Product and Department takes place in fields on the Quotations table for iOS, which is where I think the problem stems from. When a filtered selection is made it is then moved to the QuoteItems table.

Part of the confusion may come from the 'lingo'.  Practically nothing happens in FM on tables.  Things happen on Layouts and layouts are based on Table Occurrences in the graph.  That is how context is derived and context is king.  So when describing your flow, use the layout names or TO names, not table names.

 

4 hours ago, Oyseka said:

 This is the script that is used to select the Product and after Product input takes the user to the Department selection field

At first glance there is nothing horribly wrong with the script although I fail to understand the intent of the last section when you get back to Quotations.

Where physically is the user when this script runs?  In an active portal row of quoteitems on a quotations layout?

Share this post


Link to post
Share on other sites

When the script commences the user is in the Quotations layout and they only physically  enter the QuoteItems portal on the Quotations layout when both the Product and Department have been selected to select the Qty. The script above is activated by a button, Add Service, which triggers a popover with a selection field (gProdFilter) filtering a portal from the layout Prod_QuoteAll. When the Product has been selected, (the action of the script above), the user is then taken to another layout in the Quotations table (iLayQuoteDeptSelect) to select the department again from a portal from the layout DeptListAll.

Screen Shot 2017-02-27 at 16.38.14.png

Screen Shot 2017-02-27 at 16.44.06.png

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By cat traveller
      Hi everyone,
      on a file accessed via filemaker Go 17, I am using a scripted navigation to move records up and down in a portal that is inside a popover.
      This has worked in filemaker 12 like a charm and also works on a filemaker client. The records smoothly move up and down the list. 
      However in Filemaker Go, the portal follows every move of the script as if it is not aware of the freeze portal.
      EG the down button is to move the record one record further down inside the filtered and sorted portal (like so)
      This is the script.

      - freeze window and go to portal
      - go to first line of portal and loop through the portal until I hit the record to move
      - go to next line and give the position field the value of my record to be moved
      - go to line above and give the position field the value of my record +1
      - commit record and refresh portal via an x join 
      - go to last line of the portal 
      - go to the line of position of my record to be moved. 
       
      Would anyone be aware of this issue or know a workaround to stop the portal from flickering?
       
      Thanks so much
       
    • By Greg Hains
      Good afternoon,
      I am trying to understand a problem I am experiencing with an FmGo solution.  The solution is hosted on FM Cloud (AWS) and runs well on my Mac workstation, but experiences a few issues when running on the iPad.
      I'm also experiencing the same problem when I host it from a local Windows Server 2012 box.
      Using RESTful APIs (with BaseElements plugin) on my Mac workstation and I am downloading product data from a host, manipulating the data, then uploading it back to the host.
      I am assuming that I need to have the BE plugin running on the AWS host before FmGo can use the functions within. As no FM solution runs on the host itself (to Install Plugin), how do I install this plugin to the FMS there? (Assuming that this problem is related to plugins on FmGo). 
      Also, without ScriptDebugging on the iPad, I have a ton of Show Custom Dialogs all over the shop trying to see where it goes wrong on the iPad. Some of the REST calls fail with authentication errors on the iPad but work fine on the desktop. Same script. Got me beat!  I'm thinking it may be one and the same problem.
      Any help is appreciated.
      Thanks,
      Greg
       
    • By adyf
      I've just upgraded to Filemaker Pro 17 and Filemaker Go 17. Unfortunately I now get 'The Host's Capacity Was Exceeded' error message (attached) when trying to open a file on my iPad that is hosted on my MacBook. I'm the only user of this file, so it seems strange and I've never had the error with previous Filemaker versions. Has anyone any ideas please?
      Edited to add that the file opens with Filemaker Go 17 when it is open on the MacBook with Filemaker Pro 16, therefore could this be a bug in Filemaker Pro 17?

    • By Arnold Hooton
      I’m trying to retrieve a street address after I’ve used the ‘location’ function to access the gps coordinates. This may be simple but all I’m stumped. Maybe there’s a beginners tutorial on how to use url’s To get what I need. 
    • By VirtualBob
      I'm using FileMaker 12 but want to get a version that syncs via free iCloud or Dropbox type service (you can only do it manually in FM12). What is the earliest version that does this? Its for personal use and I don't have much money so I just want to get a cheap older version of FM but want it to sync across all my devices.
×

Important Information

By using this site, you agree to our Terms of Use.