Jump to content


  • Posts

  • Joined

  • Last visited

Profile Information

  • Gender
  • Location
    Los Angeles

Recent Profile Visitors

15,808 profile views

nesor's Achievements


Explorer (4/14)

  • First Post
  • Collaborator
  • Conversation Starter
  • Week One Done
  • One Month Later

Recent Badges



  1. Thanks for the tip, Wim! I've attempted to build an array in the code after looking at an example online. The dataviewer seems to show the json output matching the API spec, but I'm still getting "{"detail": "JSON parse error - Unterminated string starting at: line 1 column 25 (char 24)"}" Here's what the dataviewer now shows: { "address_from" : { "city" : "Los Angeles", "country" : "US", "name" : "KL Test", "state" : "CA", "street1" : "Thompson Ave", "zip" : "91201" }, "address_to" : { "city" : "Riverside", "country" : "US", "name" : "David Test", "state" : "CA", "street1" : "555 Some Street", "zip" : "90015" }, "parcels" : [ { "distance_unit" : "in", "height" : "5", "length" : "5", "mass_unit" : "lb", "weight" : "2", "width" : "5" } ] }
  2. Trying to integrate FMP solution with Shippo using the Shippo API. When using Insert from URL step, response comes back with this error. {"detail": "JSON parse error - Unterminated string starting at: line 1 column 25 (char 24)"} Here's what Shippo specifies in their API, and below that, what FMP is sending (per Data Viewer). Any help resolving this issue is greatly appreciated. From Shippo API: '{ "address_from":{ "name":"Mr. Hippo", "street1":"215 Clayton St.", "city":"San Francisco", "state":"CA", "zip":"94117", "country":"US", "phone":"+1 555 341 9393", "email":"support@goshippo.com" }, "address_to":{ "name":"Mrs. Hippo", "street1":"965 Mission St.", "city":"San Francisco", "state":"CA", "zip":"94105", "country":"US", "phone":"+1 555 341 9393", "email":"support@goshippo.com" }, "parcels":[{ "length":"5", "width":"5", "height":"5", "distance_unit":"in", "weight":"2", "mass_unit":"lb" }], "async": false }' Here's what FMP 16 Data Viewer shows: { "address_from" : { "city" : "Los Angeles", "country" : "US", "name" : "KL Test", "state" : "CA", "street1" : "Thompson Ave", "zip" : "91201" }, "address_to" : { "city" : "Los Angeles", "country" : "US", "name" : "David Test", "state" : "CA", "street1" : "1017 South Point View St", "zip" : "90035" }, "parcels" : { "parcels" : [ { "distance_unit" : "in", "height" : "5", "length" : "5", "mass_unit" : "lb", "weight" : "2", "width" : "5" } ] } }
  3. Trying to get FMP 16 solution to integrate with Shippo to get shipping rates but keep getting an authentication error. I suspect my syntax is wrong in the cURL component of the Insert from URL step. I've checked the URL ($url) and token ($token) and they are correct values. Any help is greatly appreciated. Shippo API: curl https://api.goshippo.com/shipments/ \ -H "Authorization: ShippoToken shippo_test_4f4d4302e76f97f922d6fb957a9c156712bec772" \ -H "Content-Type: application/json" \ -d '{ "address_from":{ "name":"Mr. Hippo", "street1":"215 Clayton St.", "city":"San Francisco", "state":"CA", "zip":"94117", "country":"US", "phone":"+1 555 341 9393", "email":"support@goshippo.com" }, "address_to":{ "name":"Mrs. Hippo", "street1":"965 Mission St.", "city":"San Francisco", "state":"CA", "zip":"94105", "country":"US", "phone":"+1 555 341 9393", "email":"support@goshippo.com" }, "parcels":[{ "length":"5", "width":"5", "height":"5", "distance_unit":"in", "weight":"2", "mass_unit":"lb" }], "async": false }' My cURL code in the Insert from URL step: "-H & Authorization: ShippoToken" & $token & "-H" & "Content-Type: application/json" & "-d" & $json
  4. Just came across this post (in June of 2015) and now I've got a solution to getting a chart to display a trend over years and months, sorted chronologically. While I had all of the components in place (calc field, sort, chart setup correctly), the calc field was defined incorrectly. I never would have figured the calc formula that @comment suggested. It worked. Thank you for the post and suggestions.
  5. Thanks for the quick answer, Comment. Yes Because it's an industry norm to round it this way. Is there a calc that can accomodate this?
  6. I'm seeking help with a calculation that would round the duration between 2 dates as follows: Fields: Rental_Start_Date Rental_End_Date Rental_Duration Rules: Rental_Duration will calculate how many weeks between Rental_Start and Rental_End date Rental_Duration can show partial week (e.g. 1.25 weeks, 1.50 weeks) Rental Duration will be rounded to 2 decimal places Rental_Duration fractional value must be either .00, .25, .50, or .75 Examples: 2 weeks, 1 day (i.e. 15 days) would be calculated as 2.00 weeks 2 weeks, 2 days would be calculated as 2.25 weeks 2 weeks, 3 days would be calculated as 2.50 weeks 2 weeks, 4 days would be calculated as 2.50 weeks 2 weeks, 5 days would be calculated as 2.75 weeks 2 weeks, 6 days would be calculated as 3.00 weeks 3 weeks, 1 day would be calculated as 3.00 weeks 3 weeks, 2 days would be calculated as 3.25 weeks so on and so forth...
  7. Your method of marking Items "Invoiced" seems to work. In the system we built at our company, Invoice Items are separate entities from Project Items — Seems to allow for most flexibility. Also, you may want to disable Field Entry in browse mode for your Invoice Report layout (Unless you want users to be able to edit data directly on the invoice.) Your layouts look great, btw. With scripting.
  8. Layout objects that don't look like they're from OS 8 (Mac). It's shocking how poor the FMP layout objects are in this day-and-age. How about OS X-looking buttons, scrollbars, tab objects, etc. for the Mac version? Multi-dimensional arrays as a native variable type. Array-based listboxes instead of Portals. Variables that can be populated in dialogs and on layouts Layouts that can inherit objects/color/style from other layouts. More flexibility over relating tables to each other (i.e. more options than = ≠ > ≥ < ≤ x) Drop down menus that utilize IDs but display names on layouts. Transactions with rollback feature. Script step to toggle all objects on a layout between Read-Write and Read-Only states. Searching in the Relationship diagram A print-friendly Data Design Report Native ability to send SMS text messages Ability for FMS to email PDFs Native functions to utilize Web Services Syncing with Filemaker Go DBs
  9. You shouldn't need an IF statement and you don't need Omit multiple records for this. Use Constrain Found Set, check the box for "Specify find requests". The Action drop down menu should be set to "Omit Records". The criteria should be Inventory::Sold = 1 When this script runs, it should leave in your current set of records only those that are NOT sold.
  10. Are the items on estimates/work orders when they're in the "Estimate" and "Approved" phase? In other words, do the items appear on quotes and if customer approves, then the items should appear on invoices? As a general rule, I think Invoice-line-items should be treated as separate entities from Order/Quote line-items. That is to say, they should exist in separate tables.
  11. Add field (of you don't have already) "Sold" to products table. Create a value list 1 with one value in it: 1 Add the Sold field to your product layout and set it up to use a checkbox. Set this checkbox to use values from value list 1. You can change the font color of the checkbox to make the number "1" disappear. Now you have a checkbox and when it's checked, the value 1 will populate in the Sold field. Method 1: Create a script to constrain your found set to omit records where Products:sold=1. Attach the script as a trigger to your checkbox. If you set it to fire when the Sale field is modified (i.e. user check or unchecks the box), you can have the record omitted from view once Sold is checked. You might prefer changing the trigger to fire when the Sold field is exited. Method 2: Add a global field to your products table gOne. Create a startup script that sets Products:gOne to 1. Create a new table occurrence (in your relationship graph) labeled "Available Products" or similar The relationship should be Products:Sold ≠ Available_Products:gOne You can create a layout based on the Available_Products table occurrence.
  12. It sounds like you may need a 2nd table for siblings. Regarding portals on a layout, double click the portal and you can change the relationship it's set to use. Double-click fields on the portal and you'll see what tables they come from (and can change them).
  • Create New...

Important Information

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