urlwithparameters() function is converting a datetime query parameter into a timestamp when other numerical query parameters are involved.https://community.appian.com/discussions/f/general/38137/urlwithparameters-function-is-converting-a-datetime-query-parameter-into-a-timestamp-when-other-numerical-query-parameters-are-involvedEarlier today I was helping another developer understand an issue involving links using a urlwithparameters() function. They were experience an issue where a datetime passed as a query parameter was reading out one minute behind in the linked interfaceen-USTelligent Community 12RE: urlwithparameters() function is converting a datetime query parameter into a timestamp when other numerical query parameters are involved.https://community.appian.com/thread/143553?ContentTypeID=1Wed, 11 Dec 2024 02:53:08 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:63677ea6-fece-4dbf-a492-df5572a9031aMathieu Drouin<p>Just reproduced on my end. Probably something you should log with Appian Support.</p> <p>datestimes, decimals in particular do not fare very well in these scenarios in general.</p> <p>IMO,&nbsp;it&#39;s always best to&nbsp;convert all parameters to normalized strings if&nbsp;you are using in a web API (either via query parameters or post body).</p><div style="clear:both;"></div>