mcschan

Hi Dana (Reed) I just tested on the web. Instant Web Publishing does not handle the invisible button properly. It takes the portal as a text field. Matthew

Hi Dana (Reed), So in your implementation, does the user click on the portal to select a Root Cause? Where does the Root Causes that the user have picked would show up in the layout? Say I click RC1 and RC3. I only see the latest one from the rounded box that you made on the side. Thanks Matthew

Hi Reed, Thanks for offer the help. I have attached the file in .zip format. The file has the username "Administrator" and no password. From the HomePage, press the "View All Order Incident Details" button. This is the layout that I am having trouble with. If you look down about the middle of the layout there's the Incident Root Cause field. I want the user to be able to enter up to 5 root causes for an incident. I let the user choose the root causes from a value list that includes both the root cause code and the root cause type, and values are automatically look up root cause types and root cause description fields. But when I web publish it, the value list only display values from the first field and all the look ups are gone! Right now, when I go into browse mode, none of the fields in the portal will show. Eventually, I want to be able to choose the department, the sales representative and the exception type, just as the way root causes are chosen and looked up, in the way you described. I also need to build a similar mechanism for querying the different incidences. If you go to HomePage then press "Select Query to View Counts" button. This will bring you to the query page and I want the user to be able to choose the root cause type and have the root cause code automatically entered. Right now this function works in FM Developer but when it's web published, everything is gone. I want the users to choose from a list because we want a finite set of root causes for the incidents (as well as sales rep, exception type, department) so the querying criteria is easily matched. I thank you a million times for helping me with this. Thank you thank you thank you... Sincerely, Matthew Order_Exception_Analysis.zip

Hi Homer, Would you be able to build a template for me? I tried putting a portal on the layout in Layout mode but nothing shows in Browse mode. Your help is greatly appreciated. Thanks Matthew

Hi Reed, Would you be able to attach a template to show how that's could be done? I am sorry I am just a beginner. Your help is greatly appreciated. Thank you. Matthew

How do I trigger a script without pressing any buttons?

Dear FM Experts, I have a major problem with my database with needs to be web published. I've defined value lists that displays values from 2 fields, it works perfectly fine until I web published it. Only values from the first field showed up. For example, I have a departments value list, with the first field being the department number and the second field being the department name. I can't just display the department name only because I used the department number to look up other things about the department. Also I've defined fields such that when I select the department, a description for the department is automatically entered. This functionality is also gone when web published. Do I have any work-arounds for this problem? Please help me as this project is nearing its deadline. Thank you very much Matthew

Alright I'll send my db to your email Jamsessionware@mac.com. It has the title "mcschan's database for tunnelling relationship, from FMForums.com" Thank you for all your help. Matthew Chan

Hi Soren Dyhr, Thanks for all the great help. I have just one final request. If you go to HomePage > Select Query to View Counts > choose a Root Cause > press View Query; this will bring you to a portal with all the incidents that had the root cause chosen. Before I switched over to the portal method of storing root causes I had this function working. However, because the link OrderIncidents::k_incidentRootCause = Root Cause Types::kp_rootCauseCode is broken, this won't work anymore. I have instead the relationship OrderIncidents::kp_orderExceptionIndex = Root Cause Portal (same as APortal):Order Exception Index and Root Cause Portal::Root Cause Code = Root Cause Types::kp_RootCauseCode (see attached picture). Would you please help me with this query? How should I relate Relationship_Root Cause so that it actually looks at the root causes in each incidence? Thank you very much. You are the man! Matthew Chan

Hi Soren Dyhr, Thank you very much for your help. Would you please explain to me how and why this works? Why does a portal work in this case? Thanks. Also, because I've made a number changes to my db since I sent you the file, I basically need to migrate what you had to mine. To get 5 rows in the portal, do I have to create 5 identical records in the APortal table linking to the same invoice number? How do I get rid of the borders of the portal? Matthew

BTW, this database that I am writing will be web published. I have value lists that displays values from two fields. However, when web published, only the primary field values are displayed, not the secondary field. How do you fix that?

Could anyone please help me here!

Hi Soren Dyhr, I should have attached it earlier but I had to get my manager's approval. I've attached it to this post. Just in case it asks for a user account, it's Admin with no password. After you opened the file, turn to the Enter Incidents layout. You'll see in the middle of the layout there are the Incident Root Cause fields. If you just click on the first field it'll show a value list whereby you can choose the predefined values. Go down a row and choose a second root cause, you'll find that the Name of the Root Cause gets placed in the first Name field. I want the second Root Cause name to be associated with the second Root Cause Code. Also if you go to the Query layout and select a Root Cause to query, it'll only look for the first Root Cause, instead of looking at all 5. Is there a way to make this query so that FileMaker looks at all repetitions? I'll read the web site you attached to see if I can make any sense out of it. Thanks Matthew Chan Order_Exception_Analysis.zip

Hi Soren Dhyr, By look up I don't mean the act of storing redundant data. All the root cause code and root cause names are stored in the Root Cause Types table. I have the relationship Order Incident::Root Cause Code = Root Cause Types::Code, and this relationship is not looked up. However, when I choose the root cause code from the value list it automatically fills in the root cause names. It is this automatic filling of the name that's causing problems for me. Thanks Matthew

I made a minor mistake on my previous post. The secondary repeating Order Incidents::Root Cause Code fields do look up for values in Root Cause Types::Name after I chose them from the value list. However, the values for Root Cause Types::Name will only be entered in the first repetition. In other words, the second Root Cause Types::Name will replace the first Root Cause Types::Name, the third will replace the first, the fourth will replace the first and the same is true for the fifth. How do I make the repeating field so that the second root cause Name will get enter into the second repetition, the third root cause Name will get enter into the third repetition, etc etc?