Hi @LucasDaniel,
Thanks for sharing.
Can you explain to me what the idea is behind the filter query. It looks like you are comparing a single line of text ERG column value with a ERG tags column value from the same library? Where does the answer of the form question come into play?
To avoid special characters of terms/tags you could use the TaxCatchAll/IdForTerm and filter on the id of the taxonomy term. This way you will get the correct term and also don't have an issue with translation of the label of the term.
If you do want to use the label of the term you could use the encodeUricomponent function. This would turn the query into a valid query. This does mean that the value of the ERG column needs to be written as D%27Origine to return a match.
ERG eq '@{encodeUriComponent(item()['Label'])}'
On a side node, you could also use TaxCatchAll/Term for your filter. However, I do not prefer that because duplicate labels could exist in a taxonomy.
Mikael Svenson has a great blog about the TaxCatchAll filtering:
https://www.techmikael.com/2016/05/workaround-to-filter-on-taxonomy.html