ShaneMiller
Qrew Trainee
Joined 3 years ago
User Profile
User Widgets
Contributions
Re: Formula Text/ Date Wizard Needed
Thank you for replying Chayce. What you came up with is really impressive. When inputting the date 01-01-1992 I get the result of "For 31 years, 10 months, 34 days". Obviously this has to do with the leap yea you mentioned. I will try tinkering with it to see if I can figure it out. It is way further than I was able to do, so either way I am satisfied. Thank you! ------------------------------ Shane Miller ------------------------------8Views0likes2CommentsFormula Text/ Date Wizard Needed
Hello, I have one date field called "Original Effective Date" that is referring to the first day a client began working with us. I want to have 1 formula text field that utilizes the today() function to say: [Employer ID] has worked with us for _ years, _months, and _days. What would be the best way to accomplish this? ------------------------------ Shane Miller ------------------------------15Views0likes4CommentsPipelines | Multi-Select Text | Duplicates
Hello, My scenario has to do with baseball and creating rosters based on a persons preferred positions. Here is my scenario: Step A: Search Table 'Players' (Players table pulls in Text Field with the [Name] and a multi-select text with the persons [Preferred positions]) Query- no filters Step B: Search Table 'Game' (Game table pulls in Multi-Select [Attendance] with the Players that will be at that game, and multi-select fields for each position [catcher][pitcher][1st base], etc) Query- [B.Attendance] contains [A.name] (this only pulls people in that specific game) For Each B, if the Table A [A.Preferred_Positions] contains Catcher Then Update Record B Games table: B.Catcher Field jinja: {% if b.catcher == none %} {{ a.name }} {% elif b.catcher != none %} {{ [a.name, b.catcher]|join(' ;') }} {% endif %} I recreated the for each loop with the condition for each position and then update each position. It works great during the first run, flawless. Pipelines will add each person's preferred fields to their assigned positions in the games table. I then have 9 positions with all the possible configurations for who can play that spot on the field. The issue I am having arises when someone texts and says they'll be at the game after I have already ran the pipeline. I add the new person and run the pipeline, and it duplicates every person that was already in the catcher position, pitcher positions, 1st base position, etc. My question: Is there Jinja2 code or a Pipeline technique that can re-run this pipeline and not re-add the same individuals who are already on a multi-select position(s) field on the game table? ------------------------------ Shane Miller ------------------------------54Views0likes0CommentsRe: Using multi select field in pipelines
I had the same issue, I was able to bypass this by adding jinja to the multi-select field in pipelines. In order to start the JINJA2 process for a multi-select field you must first drag and drop from the list of the table you desire a field into the multi select field. Once that happens, you can then create Jinja2 code. This was my code to fix the error you are speaking of: B.Field is my multi-select field on Table B that will be receiving data A.Text is my text field on Table A {% if B.Field == none %} {{ A.Text }} {% elif B.Field != none %} {{ [A.Text, B.Field]|join(' ;') }} {% endif %} Hope this helps! ------------------------------ Shane Miller ------------------------------153Views0likes0Comments