Jump to content

Roeland De Windt

Members
  • Content Count

    20
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Roeland De Windt

  • Rank
    member

Profile Information

  • Title
    IT manager
  • Industry
    Advertising
  • Gender
    Male
  • Location
    Belgium
  • Interests
    Back from FMP v6
  1. Here's the script doing that. It takes 3 scriptparameters; "first" (on the only visible "Help" button), "next" and "last" (used in balloons). A bit rudimentary, but it works. Even after changing layout, the $$help variable is always reset to 1 when first called with the visible "Help" button. The balloons have been named "Help #" sequentially. A bit rudimentary, but it works. If [ Get ( ScriptParameter ) = "First" ] Set Variable [ $$Help; Value:1 ] End If If [ Get ( ScriptParameter ) = "Next" ] Set Variable [ $$Help; Value:$$Help + 1 ] End If If [ Get ( ScriptParameter ) = "Prev" ] Se
  2. For a solution I would like on-screen help. I was thinking about using sequential popovers, taking a user in logical steps through elements and functions on a layout. Much like one would often see when using an iPhone/Android/web application for the first time. I have gotten as far as putting some (invisible) popover buttons on a layout. I have given their popover balloon a layoutobjectname, so I can use Go To Object to call and show them. I call the first one directly with a (visible) "Help" button. The problem I run into is that I would like to be able to navigate from one balloon to th
  3. @comment But... ...don't know what to say honestly. This is my relationship diagram (ANSWERS cyan on the left, REMARKS green next stack middle), is it wrong then? It works perfectly for showing groups of answers (defined by QuestionPool_ID) for an employee (Emp_ID_Evaluated) with a general remark alongside it. @dwdata Thanks for that! Scripting to the rescue.
  4. Forgive me if this has been aswered before, but couldn't find anything that answered my question. Table ANSWERS Table REMARKS In the relation definition between them, I have the ANSWERS on the left, and REMARKS on the right side, with Allow Creation and Delete Parent checked on the right side. Now the situation is that there can be multiple ANSwers with one and the same REMark. In effect, For each of the ANSwers, the same Remark will be shown. This is desired behaviour. If I delete 1 (out of ex. 3 ANSwers), the sole REMark is deleted as well. I was hoping to be able to de
  5. Final solution, after comment's last post (clarifying the non-security issue in ANSWERS table depending on role)... Manager Role, View privset: not IsEmpty ( FilterValues ( zc.Emp_Manager_UPN ; Z_GlobalValues::CurrentAccountName ) ) or not IsEmpty ( FilterValues ( zc.Emp_Evaluators_UPNs ; Z_GlobalValues::CurrentAccountName ) ) Manager Role, Edit privset: not IsEmpty ( FilterValues ( zc.Emp_Evaluators_UPNs ; Z_GlobalValues::CurrentAccountName ) ) Evaluator Role, both View and Edit privset: not IsEmpty ( FilterValues ( zc.Emp_Evaluators_UPNs ; Z_GlobalValues::CurrentAccoun
  6. Manfred should not be able to change answer fields in any record but those where he is listed as evaluator. I have already limited this Edit access for the manager privset: If ( PatternCount ( Get ( LayoutName ) ; "Manager" ) ; // should be rewritten as 'not isemtpy filtervalues' like in View privset 0 ; PatternCount ( Evaluators ; Z_GlobalValues::CurrentAccountName ) // should be rewritten as 'not isemtpy filtervalues' like in View privset ) This works. No edit access on manager layout (0) for anyone (view yes, only if listed as manager), and on the evaluator layout only edit access wh
  7. Yes there is a point to deny imho... MANfred has role MANager, EVEline has role EVAluator (role = privilegeset). Record 1: Manager field = Manfred, Evaluator field = Manfred, Answer field = x1, EmployeeName field = y1 Record 2: Manager field = Manfred, Evaluator field = Eveline, Answer field = x2, EmployeeName field = y2 Record 3: Manager field = Manfred, Evaluator field = SomeOneElse, Answer field = x3, EmployeeName field = y3 Eveline will have access to Evaluators layout only, and see only records with her name in Evaluator field (Record 2 in this case) so that's no proble
  8. Thanks Steven, I see "LayoutNames, ... since they can be spoofed" under the Inappropriate column, and not endorsed as Best practice. But should or should it not work technically? Shouldn't FMP throw an error if I try to use them? Or do they work from a technical pov, but is my syntax wrong? Any workaroud to accomplish the same thing?
  9. One table ANSWERS, 2 fields EVALUATOR and MANAGER (and a lot of others with more data), 2 layouts Evaluator and Manager, based on the same table. I want to hide records based on the layout AND the current logged in user's appearance in either of the 2 fields. (Managers should only see records when they are in the Manager field, and Evaluators when in the Evaluator field). The Manager layout is not accessible by Evaluators. The Evaluators layout is accessible by both roles (as some Managers are also Evaluators). Now I have a "Limited..." View restriction for Privilege set "Evalua
  10. Duh! Changed my conditional to: ValueCount ( FilterValues ( QUE::Emps ; QUE_ANS::_Emp_IDfk ) ) Seems to work! No pre- or post-pending needed. A lot cleaner. Thanks again, comments
  11. I elaborated a bit on this technique, more specifically the showing/hiding of things in portal rows based on conditionals. I wanted to show or hide a "delete portal row" button in a QUE_ANS portal on a QUE layout using this conditional statement PatternCount ( QUE::Emps ; QUE_ANS::_Emp_IDfk ) > 0 QUE::Emps is a multi-line field holding Employee IDs. QUE_ANS is a portal on the QUE layout, based on QUE::__Question_IDpk = ANS::_Question_IDfk. QUE_ANS::_Emp_IDfk is a single-line field holding an Employee ID. My challenge is to SHOW the "delete portal row" button on a row in
  12. In short: can I use relations with variables instead of fields. Guess not. Got it working with a global. A non-issue I just would like to see confirmed.
  13. Good questions, comment. Bare with me as I explain in more detail. TableA contains evaluation questions, 1 per record. Every record has a multi-line employeeID field holding IDs of employees in TableB, who will be evaluated. How this multi-line field is populated is beyond the scope of my question, but the bottom line is that I didn't go for a many-to-many relationship setup. To assign questions to employees, I've created a third TableC, where later on, an evaluator of the employee will need to put his answer. Now to create a record in TableC, I need to get the TableA::Question
  14. Situation: a TableA with record(s) containing a multiline field (which happens to be a multi-line key) which I am looping through in a script. I need to lookup a related value from another TableB on each loop. Currently I have to set a (global) field in TableA to the n-th value of the multiline field at each loop and pull the related value from a relation based on that (global) field (TableA_TableB). Question: is there a way to script this using only variables? ie: Set $SomeRelatedValue = LookupValue ( TableA_TableB::LookupField , $SomeGivenValue ) or: Set Field [ TableA::SomeRe
×
×
  • Create New...

Important Information

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