<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Topics tagged with patch]]></title><description><![CDATA[A list of topics that have been tagged with patch]]></description><link>https://fusionauth.io/community/forum/tags/patch</link><generator>RSS for Node</generator><lastBuildDate>Thu, 10 Sep 2026 16:03:45 GMT</lastBuildDate><atom:link href="https://fusionauth.io/community/forum/tags/patch.rss" rel="self" type="application/rss+xml"/><pubDate>Invalid Date</pubDate><ttl>60</ttl><item><title><![CDATA[Patching the user object with the java client?]]></title><description><![CDATA[<p dir="auto">I see patchUser here:</p>
<p dir="auto"><a href="https://github.com/FusionAuth/fusionauth-java-client/blob/1.19.0/src/main/java/io/fusionauth/client/FusionAuthClient.java#L1664" rel="nofollow ugc">https://github.com/FusionAuth/fusionauth-java-client/blob/1.19.0/src/main/java/io/fusionauth/client/FusionAuthClient.java#L1664</a></p>
<p dir="auto">I think that's what you want.</p>
<p dir="auto">You can, however, always full retrieval and a put as a workaround. That is recommended if you are changing an array, unless you want the behavior documented here: <a href="https://github.com/FusionAuth/fusionauth-issues/issues/441" rel="nofollow ugc">https://github.com/FusionAuth/fusionauth-issues/issues/441</a></p>
]]></description><link>https://fusionauth.io/community/forum/topic/759/patching-the-user-object-with-the-java-client</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/759/patching-the-user-object-with-the-java-client</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Invalid Date</pubDate></item></channel></rss>