• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About cos

  • Rank

Profile Information

  • Gender

FIleMaker Profile

  • Profile Updated
  • FM Application
    15 Advanced
  • Platform
    Mac OS Sierra
  • Skill Level
  1. I haven't tested. Not upgraded to v16. I develop and maintain just one FM solution in my company. It is about 10 years old and is kept up to date and feature rich. I'm just doing my homework before upgrading. Soon, I will get into testing. I guess I should call 360works. They are really great people and located only about 20 miles from our business.
  2. This is in the changeling for SC which, if correct, seems to indicate a real and positive move forward same as the other 360works plugins. Version 2.9501 (5/10/2017) Companion plug-in now runs on latest 360Works plug-in platform, with these features: *No longer requires Java installation *Can use plugin functions as script steps with a user-friendly GUI for specifying parameters *Better error reporting in scripts *Compatible with FileMaker Cloud *Better compatibility with FileMaker Server for Perform Script on Server and scheduled scripts *Each plugin runs in a separate process, increasing reliability and stability *Plugins can be reliably unloaded, making it possible to auto-update without restarting FileMaker *Where appropriate, plugin parameters can be selected from pull-down lists and checkboxes *Support for streaming large container data, allowing unlimited amounts of data to be transferred between FileMaker and the plugin without running out of memory. *Compatible with the older plugin API, so you can continue to use your existing scripts and calculations with the new plugins.
  3. Thanks sijmons. I did read this on 360works site today. "The SuperContainer Companion Plugin has been updated with new features for FileMaker 16. It is available as a minor point upgrade, at no additional cost for existing SuperContainer license holders." I hope there are plans to do a full update to SC. It really is so much easier to work with than FM containers. Would be nice to hear some official word posted here. And Bruce, you're correct. I should have mentioned 360works in the title. Didn't think about that because this is the Supercontainer forum.
  4. I didn't see any specific mention of SC in the new platform for FM16. Just that all plugins are compatible. What does this mean? Is this the end of the road for SC?
  5. pinging to bring this up again with a visual. This started happening in the middle of the day and has persisted since then. The extra return is in Filemaker, but is not in the mysql data. Anyone have a clue?
  6. We have a mysql table in FM that seems as though it could be reacting to a FM bug. I don't think this field has been altered recently, but something changed on Oct the 7th, 2016. The field contains 1 to 7 lines of text. There are no extra returns after each line of text. Not in the mysql data. Not in Filemaker. Suddenly on the 7th, the data has an extra return for each line of text. Field format settings look correct. First part of the day it was like this: Line 1 Line 2 Line 3 Line 4 and then it suddenly changed to Line 1 Line 2 Line 3 Line 4 What could cause such a thing and what can we do about it? For now, I guess a calc to strip the returns?
  7. Thanks to all. David's solution is correct. Man, how easy it is to miss the small things.
  8. I have run the Script Debugger multiple times comparing successful page and unsuccessful. It fails at line 2 of the first script. It opens the wrong layout. I can't get past that. But, I did not use the Data Viewer (doh). It is returning unusual data at line 2 which the other layouts are not. Name: rtd_orders::insert_date Value: 8/18/2016 Type: Date That's an old date. Making your suggested changes (which i did, thanks) doesn't matter because it never gets to that script because the first script opens the wrong layout.
  9. This is the new window script that works on all layouts except the Orders List layout: Sales Orders Scripts: Sales Orders Payments: PP - Goto Payments Layout New Window [ Style: Document; Name: "Paypal Payments IPN"; Top: 0; Left: 300; Close: Yes; Minimize: Yes; Maximize: Yes; Zoom Control Area: Yes; Resize: Yes ] Go to Layout [ “Paypal Payments” (paypal_ipn_orders) ] This script trigger runs on layout enter: Sales Orders Scripts: Sales Orders Payments: PP - Open List - Adjust Window Resize to Fit Show ... Allow User Abort [ On ] Show All Records Enter Find Mode [ ] Insert Calculated Result [ paypal_ipn_orders::creation_timestamp; " > " & Get ( CurrentDate ) - 7 ] [ Select ] Perform Find [ ] Sort Records [ Keep records in sorted order; Specified Sort Order: Payments Status::MAP Status; descending paypal_ipn_orders::id; descending ] [ Restore; No dialog ] Scroll Window [ Home ] Adjust Window [ Resize to Fit ] Move/Resize Window [ Current Window; Height: 1100 ] Show/Hide Toolbars [ Hide ] Halt Script The Orders List layout also has a script trigger on layout enter: Online Orders Scripts: OO - Open List - Adjust Window Resize to Fit Show All Records Sort Copy Enter Find Mode [ ] Insert Calculated Result [ rtd_orders::insert_date; " > " & Get ( CurrentDate ) - 6 ] [ Select ] Perform Find [ ] Sort Records [ Keep records in sorted order; Specified Sort Order: rtd_orders::order_id; descending ] [ Restore; No dialog ] Adjust Window [ Resize to Fit ] Move/Resize Window [ Current Window; Height: 1100 ] Show/Hide Toolbars [ Hide ] Scroll Window [ Home ] Halt Script
  10. I have a Payments List View layout that can be opened from any layout using: New Window . . . Go to Layout . . . Except this one other List View layout. It just ends up as a new window of the same layout. New Window . . . Go to Layout . . . will not open any other layout. Driving me nuts. What causes this? FM15 Advanced
  11. All week I have read up on how to set the variable and set the fields in a loop and cannot figure this out. This is my first try at the Let function. It's pretty versatile. It's hard to find examples of how to use it all together in a script. Could you give an example of Set Variable and Set Field using Loop and your rules?
  12. Ah. You are right about the commas. I got mixed up with the previous extraction being one field. The Quantity is a separate field from the rest of the infos in the source and it is joined in the export. Yes, "},{" would give us a carriage return to loop. I can restructure the data a bit that may give a consistent structure by placing Item_ID at the start like this: [{"":"2","unique:2[]":"00254 | Machines | 2.75’’x5.25’’ (1390-LAB 3) vinyl laminated 290 4 to a sheet"},{"":"34","unique:2[]":"00249 | Misc | 2.75’’x1.236’’ (Proudly Built) vinyl laminated 290"},{"":"10","unique:2[]":"00266 | Redbox | 7.9\"x 3.9\" (RBL_outline) vinyl laminated 290"}] Which would always render exactly the same except qty would be 1-4 digits {"":"2","unique:2[]":"00254 {"":"34","unique:2[]":"00249 {"":"10","unique:2[]":"00266
  13. And now for part 2 and final of this extraction. We have another text field that is very similar, but has some distinct differences. The text contains a series of data to be placed in Line Items. Each Line item looks like this: Item_ID Description Quantity The imported data always looks like the following example for 3 line items, but there could be many more. Commas separate each set of line items. There will never be a comma elsewhere. [{"":"2","unique:2[]":"Machines | 00254 | 2.75’’x5.25’’ (1390-LAB 3) vinyl laminated 290 4 to a sheet"},{"":"34","unique:2[]":"Misc | 00249 | 2.75’’x1.236’’ (Proudly Built) vinyl laminated 290"},{"":"10","unique:2[]":"Redbox | 00266 | 7.9\"x 3.9\" (RBL_outline) vinyl laminated 290"}] There first "2" is the Quantity. "00254" is the Item_ID Quantity and Item_ID are all we need to extract for each line item because the description is already in Filemaker with the Item_ID I appreciate any commentary.
  14. Okay. I get it. Done. Works perfectly. You are the champ.
  15. Thanks for this. I understand the Set Fields. I'm a bit confused with the variable. After studying your solution, I think for my understanding, it might be better to replace " | " with simply "|" in the source text. So an actual real world text string would look like this: [{"":"The Test Company|John Doe|1234 Main Street|Beverly Hills|CA|91210"}] In this example "Ship To" is replaced with "" Seems that the source always sends "" for a non-entry in that part. Looking forward to your solution.