Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 03/19/2021 in all areas

  1. No, you wouldn't. You will see why in a moment. In order to produce a return-delimited list of individual count of each value, you could do a calculation like this: While ( [ listOfTypes = YourSummaryField ; uniqueTypes = ValueListItems ( "" ; "YourValueListName" ) ; n = ValueCount ( uniqueTypes ) ; i = 1 ; result = "" ] ; i ≤ n ; [ result = List ( result ; ValueCount ( FilterValues ( listOfTypes ; GetValue ( uniqueTypes ; i ) ) ) ) ; i = i + 1 ] ; result ) This will return a list of counts of each value, in the order of the value list. But for a chart - esp. if it is a pie ch
    2 points
  2. Berlin, 19. April 2021 - herrfriedrich.com, a long-time FileMaker Certified Developer and Claris Platinum Partner is pleased to announce that registration for dotfmp.berlin 2021 is open and can be accessed here: https://dotfmp.berlin dotfmp.berlin is an effort of various European FileMaker Developers and takes place in Berlin, Germany each year starting at the first Thursday in June. dotfmp.berlin is a 3 Day-Unconference and as such by definition an informal and self-organized effort to meet on a personal base. It is meant to bring all kinds of higher level developers together to share
    1 point
  3. There are several ways this could be accomplished - here is one: Chart3monthsR.fmp12
    1 point
  4. The Get() functions are not script steps they are available in the calc engine inside a Set Variable / Set Field or Set Calculated Result
    1 point
  5. Actually, it is not similar at all - and you would have done better to post this as a new question. Filemaker has no conditional aggregate functions similar to Excel's SUMIF() and COUNTIF(). There are several alternatives: 1. Use a summary field defined in the child table. Place this field in a one-row portal, filtered to show only records that meet the condition. This is suitable when the number of child records is not very high and the result is for display only. 2. Define a second relationship that matches only child records that meet the condition. Then use a calculation fie
    1 point
  6. I would suggest having a relationship between the two tables. This would not only make creating the "master" record easier, but also eliminate completely the possibility of creating it more than once.
    1 point
  7. Ok, that is reasonable. But in such case you want your delimited lists to be produced by a script and written into global fields or variables. (Note the plural form: you need one list for the X axis and another for the Y axis - and you need to produce them in corresponding orders.) Which means the chart must be produced/updated on demand. IMHO, the Fast Summaries method would be indeed the best way to produce such lists. Alternatively, you could also use ExecuteSQL().
    1 point
  8. What you've quoted is a Response—note the <InvoiceAddRs> and </InvoiceRet> tags. I wouldn't expect that result from a PCQB_SGetXML( "Request" ; "" ) call. There should be no issue identifying a SalesRep in an InvoiceAddRq. You'd normally pass the value in a PCQB_RqAddFieldWithValue( "SalesRepRef:ListID" ; "..." ; "" ) or PCQB_RqAddFieldWithValue( "SalesRepRef:FullName" ; "Initials" ; "" ) call. I'm wondering if there's an issue with the ambiguity between the SalesRep's ListID and SalesRepEntityRef:ListID. You want to pass the former, not the latter. If you're passing Sale
    1 point
  9. But there is a problem. Besides all the other flaws of this method that have been pointed out above (and which the OP apparently chose to ignore), there is the problem of getting incorrect results in case of a tie.
    1 point
  10. JJAllison1, This solved my problem, too easy of a solution, I had tried everything else and had become discouraged thinking that Filemaker 15 was simply conflicting with the new apple OS. THANKS!!!
    1 point
  11. This is an old post, but I had the same problem, this is how I solved it. 1. Delete FileMaker go 15 from the ipad 2. Open the app store 3. Click on your picture 4. Click purchases 5. At the top, switch to “not on this iPad” 6. Scroll down to “FileMaker go 15” 7. Click download (the little cloud icon)
    1 point
  12. I think it depends on how you intend to select that particular person's name. Selecting a value out of ~1000 possible alternatives is not an easy task for the user. Once you have the selected name, you could calculate its position in a list of names provided by a summary field, defined as List of [ PlayerName ], and use this to go to the corresponding record. The calculation would be something like: ValueCount ( Left ( sListOfNames ; Position ( ¶ & sListOfNames & ¶ ; ¶ & selectedName & ¶ ; 1 ; 1 ) ) ) Alternatively, you could just loop over the found set until you h
    1 point
  13. Yes, it would. You say you only have 4 users now - but users come and go. Adding/deleting a user should not require a change in the file's schema. If you want to keep this simple, then use a single text field that stores a return-separated list of the users (or, preferably, account names) that have viewed the record. Then it's easy to apply conditional formatting using the expression = IsEmpty ( FilterValues ( Get ( AccountName ) ; YourTable::ViewLog ) ) --- Note that keeping the view log within the record itself means that the record will be modified anytime someone views it for
    1 point
  14. https://firesidefilemaker.podbean.com/e/punishing-performance/ In this PodCast, we highlight yet another hero in the FileMaker market, Wim Decorte of Soliant Consulting. As long as there has been FileMaker, it seems like Wim has been there helping people on the message boards, writing white papers and presenting at Claris DevCon/Engage. He even created an open source FileMaker product, called the Punisher, aimed at testing a FileMaker solution over the network. We’ll discuss the Punisher and where you can get it, as well as optimizing performance on FileMaker Server, FileMaker Pro and Fil
    1 point
This leaderboard is set to Los Angeles/GMT-07:00
×
×
  • Create New...

Important Information

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