Jump to content


Popular Content

Showing most liked content since 10/20/2017 in Posts

  1. 2 points
    I don't understand the question. It seems to me like you've already identified what needs to be done. I would recommend breaking it down and getting one portion working at a time, doing whatever research/experimenting you need to figure out each step. If you searched through the help file, I think you'd find you can piece this together. For your first step "Open Find" for example, you might want to read this: https://fmhelp.filemaker.com/help/16/fmp/en/#page/FMP_Help%2Ffind-request.html. The reference section of the help is useful for exploring what script steps are available: https://fmhelp.filemaker.com/help/16/fmp/en/#page/FMP_Help%2Fscript-steps-category.html%23 Here is some more general help on writing a script: https://fmhelp.filemaker.com/help/16/fmp/en/#page/FMP_Help%2Fscripts.html%23
  2. 1 point
    Here's a demo. However, there is no check to see if there already is a record with the stat for this player (that is, no check for duplicates). Also, what happens if you add a stat? You'd need a script to add that stat to the players_stats table for each player. xydudyax.fmp12
  3. 1 point
    You will have to script record creation. You can either place a portal on the layout and go to that object or you can go to the native layout and create a records there. I recommend learning about ERDs. You can use Google, there are tons of examples out there.
  4. 1 point
  5. 1 point
    http://filemakerinventoryresources.com But I agree, I don't think you realize that this is quite a complex system you might need.
  6. 1 point
    I've asked my fair share of questions and received tons of help on the forums. But in this case, with an inventory tracking database, bar codes, multiple users (server?), syncing data-it's quite complicated. If it were me, I would consider looking for a FileMaker developer to, at the very least, set this up to get the ball rolling. Proper fields/calculations & relationships are a must. You could spend a huge amount of time going down the wrong path, only to have to start over. I'm not saying you couldn't figure it out, with some help here, and everything will be fine. I'm saying I would at least want the initial (proper) structure set up, and know it's correct.
  7. 1 point
    Save your json to a variable, like $requestData, then add this curl option: --data @$requestData Here is a useful post on the topic: https://community.filemaker.com/docs/DOC-8025
  8. 1 point
    Greatly! Got me to where I figured it out. I added a third relation between the two tables and added a auto-field which filtered the statuses automatically. Thanks!
  9. 1 point
    Hi becham, I would do this with a Conditional Formatting if you only want to view them. Example file shows two different colors, one for past and one for future of the target date. You could use the same color for both fields AnyDate represents your date field (you mentioned in your post). Flag.fmp12
  10. 1 point
    Use the Date( ) function to create dates 56 days before and after your expiry date, and use that in the Set Field script step. The Date( ) function takes care of months and years all by itself. Enter Find Mode [ ] Set Field [YourTable::ExpiryDate; Let( [~theDate = YourTable::ExpiryDate; ~start = Date(Month(~theDate); Day(~theDate)-56; Year(~theDate)); ~end = Date(Month(~theDate);Day(~theDate)+56; Year(~theDate)) ]; ~start & "..." & ~end ) Perform Find [ ]
  11. 1 point
    H Kyre and welcome to the FM Forums, First question (provided someone who has used "WooCommerce" in this manner already jumps in) is, what formats does WooCommerce import and export?
  12. 1 point
    I used the GetAsNumber function to save a pile of parsing out brackets. This resulted in expected behavior for numbers: FileMaker strips leading and trailing zeros from numbers. Add the following lines to the script Set Variable [$lat; Value:GetAsNumber(Right ($currVal ; $valLength -$firstComma ))] #--------Add these lines after above current line in script--------- If [Abs ( $lat ) <1 and $lat < 0] Set Variable [$lat; Value:Substitute ( $lat ; "-" ; "-0" )] End If If [Abs ( $lat ) <1 and $lat > 0] Set Variable [$lat; Value:"0" & $lat] End If #------------------end add lines-------------------------- Set Variable [$output; Value:$output & "[" & $lat & "," & $long & "],¶"] This works only because FileMaker is quite sloppy about typecasting numbers and text.
  13. 1 point
    Hi muskee You need to add accounts to Database B with exactly the same username and password as you have in Database A. That way, FileMaker will try to open Database B with whatever name/password was used to open Database A and show the data without asking for login. If there is not a matching account in database B, then you will be asked for login credentials. There is no way to tell FileMaker to use a specific name/password when opening a file that is referenced in 'Manage -> External Data Sources', you have to do what I describe above.
  14. 1 point
    Two ideas: Create another field, type text, with an auto-enter calc = getastext(barcode_graphic). Set that field's validation to unique. or Create another field, type text, with an auto-enter calc = Base64Encode ( barcode_graphic ). Set that field's validation to unique.
  15. 1 point
    Open the Conditional Formatting on the balance, and change the the purple (the color of the text in the rest of the layout) to Green.
  16. 1 point
    One more thing I've noticed ... Your Services and Rent History tables do not appear to have a unique ID. You really should have one in every table. If you ever lost your data or had to restore, you would use this unique ID to update/correct or replace the records. It's more than just used for a relational key. Without knowing your business quite a bit more, I am only guessing here but I would consider the RentalHistory more the 'contract period'. If rent can change over time, the rental agreement on the monthly charge would be in Rental History ... charge THIS Tenant THIS much for THIS property for this timeframe. Your Invoices should be related to this RentalHistory table as: 'this invoice is charged to this tenant during this rental agreement for this property. I guess that was two things, LOL.
  17. 1 point
    That is fine. And, as you have it, one Tenant can be 'paying' for, or be responsible for, one or multiple Property Listings. I would suggest that what you consider 'Rent History' should actually be a join table between Property and Tenant. Join Property_IDFK from Property to RentHistory. Then join Tenant_IDFK over to Tenant. This allows more flexibility, such as a Tenant leaving then coming back and it allows one Tenant to be responsible for multiple Properties etc.
  18. 1 point
  19. 1 point
    I deleted you duplicate Question. Please do not multiple post your questions.
This leaderboard is set to Los Angeles/GMT-08:00

Important Information

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