Good evening I have tried to use pulldata(@layer) to automatically fill in a text in a form I want as a calculation where the date of form 1 must be equal to the date of form 2 to be able to use the filtered feature
This is one of the conditions with pull data:
pulldata("@layer", "getValue", "attributes.descritivo_comportamento_de_fog", "https://services-eu1.arcgis.c om/VlrHb7fn5ewYhX6y/arcgis/rest/services/survey123_bd2f7d69157440b3b88384238c9f8a4e/FeatureServer/0", "(dia_em_an_lise NOT BETWEEN CURRENT_TIMESTAMP - 3 AND CURRENT_TIMESTAMP) AND (classe_dia = 'Day 1')")
the code like this is functional but not as I intend it to filter
so its this:
pulldata("@layer","getValue","attributes.meteo_d1",${url}, ${where_clause})
where_clause is: concat("dia_em_an_lise=", ${d1})
The answer is this
Should fill in the text in Meteo D1
And did nothing
In short, the idea is that you fill in the text of an uploaded report in which only the text of the record of the day under analysis is equal to the date uploaded to the form.
Form Date:
Field to be filled from another outer layer:
Thanks
Solved! Go to Solution.
This is the solution that worked:
"dia_em_an_lise BETWEEN CURRENT_DATE AND CURRENT_DATE + INTERVAL '1' DAY - INTERVAL '1' SECOND")
It's not bad, but it's too complex for such a simple mind-reading and limits the construction of conditions.
I think ESRI should consider allowing the use of this type of condition even in web search, in the same way it exists in the experiment builder.
It's not bad, but it's too complex for such a simple mind-reading and limits the construction of conditions.
I think ESRI should consider allowing the use of this type of condition even in web search, in the same way it exists in the experiment builder.
In short, it does not facilitate the dreamed dynamics in their entirety.
This is the solution that worked:
"dia_em_an_lise BETWEEN CURRENT_DATE AND CURRENT_DATE + INTERVAL '1' DAY - INTERVAL '1' SECOND")
It's not bad, but it's too complex for such a simple mind-reading and limits the construction of conditions.
I think ESRI should consider allowing the use of this type of condition even in web search, in the same way it exists in the experiment builder.
It's not bad, but it's too complex for such a simple mind-reading and limits the construction of conditions.
I think ESRI should consider allowing the use of this type of condition even in web search, in the same way it exists in the experiment builder.
In short, it does not facilitate the dreamed dynamics in their entirety.
The fields you are pulling the attributes from is different between the 2 pulldata functions you are using.
"attributes.descritivo_comportamento_de_fog" in the working one and "attributes.meteo_d1" in the one that isn't working, which is also what is in your xlsform. I can't open the url for the service you are trying to query to see the fields in it, so this is a guess, but I would try it as:
pulldata("@layer","getValue","attributes.descritivo_comportamento_de_fog",${url}, ${where_clause})
in your form and see what happens.
Olá, este é o mesmo código que estou usando, mas já vi que o formato da data é xy/xy/xyzx e 00:00 não entendo que não consegui obter o texto referente a esta expressão
Você quer que eu mostre os campos?
I've sabotaged myself by referencing the wrong field and seen others do it too. It is almost always the easiest fix, but the hardest for us to find because we stare the spreadsheet for so long. It looks like that isn't your problem.
This is the solution that worked:
"dia_em_an_lise BETWEEN CURRENT_DATE AND CURRENT_DATE + INTERVAL '1' DAY - INTERVAL '1' SECOND")
It's not bad, but it's too complex for such a simple mind-reading and limits the construction of conditions.
I think ESRI should consider allowing the use of this type of condition even in web search, in the same way it exists in the experiment builder.
It's not bad, but it's too complex for such a simple mind-reading and limits the construction of conditions.
I think ESRI should consider allowing the use of this type of condition even in web search, in the same way it exists in the experiment builder.
In short, it does not facilitate the dreamed dynamics in their entirety.
My guess is that the date in your "where clause" does not match the date in the layer you are pulling from. For example if you used now() in your pull data layer, the date would include time as well. You are using today() in this form and that formats date with default time. Check to see that your date formats match between the 2.
Passei de today() para now() e ainda não aparece o texto me deixa triste é que usar uma expressão diferente não funciona, e mesmo criando formatação de teste nada funcionou, o formato foi configurado e mal configurado e continua o mesmo
The field you are pulling from is a String field according to your screenshot above. You are trying to match to a date formatted to UTC. You will need to format one of those to match the other. Not sure how you are getting the date populated to meteo_d1, but your field right before it "data" is a date field. If the date in that field is the same as the date in meteo_d1 you could try that field for your pulldata calculation.
https://community.esri.com/t5/arcgis-survey123-blog/dates-and-time-in-survey123/ba-p/895528
This is the solution that worked:
"dia_em_an_lise BETWEEN CURRENT_DATE AND CURRENT_DATE + INTERVAL '1' DAY - INTERVAL '1' SECOND")
It's not bad, but it's too complex for such a simple mind-reading and limits the construction of conditions.
I think ESRI should consider allowing the use of this type of condition even in web search, in the same way it exists in the experiment builder.
It's not bad, but it's too complex for such a simple mind-reading and limits the construction of conditions.
I think ESRI should consider allowing the use of this type of condition even in web search, in the same way it exists in the experiment builder.
In short, it does not facilitate the dreamed dynamics in their entirety.