Latest Contributions by TJSimons

Hi @GopinathJayakumar  - For this workflow you will not need the trial.  Only the Location Platform account you created.  Location Platform has access to an ArcGIS portal. Use this workflow to create an API Key: Tutorial: Create an API key. At the end of the workflow, you will have an option to generate and copy your API key.  Is the API key not generating?  If not, are you seeing any errors pop up or in the browser console? Thanks, TJ ... View more

Hi @VenkataKondepati - I recommend logging a case with Support, https://support.esri.com/en-us/contact.  We will be able to look at this more closely with you.    ... View more

Hi @QDSGIS - This looks like it might be a service issue rather than a Print Widget issue.  Can you open a Tech Support case so that it can be investigated further?   ... View more

Hi @QDSGIS  - Do you have a sample that demonstrates the issue?  Any change in the behavior at 4.30?  Thanks.  ... View more

Hi, You could try passing the parameters in the URL of the GET request in the body of the POST request by using the body parameter of the xhttp.send() method. https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest/send You could also use form data. https://developer.mozilla.org/en-US/docs/Web/API/FormData/Using_FormData_Objects ... View more

Hello Hamza Boudemia,   The Windows account should be able to generate a token.  Portal's identity store has to be updated to use Windows accounts and the account needs be added as a member to Portal.  If the account is not added as a member you would receive the "Invalid username or password" error.   Otherwise, it is likely that the username or password is incorrect.  The username needs to include the domain for Windows accounts.  Providing the username without the domain will return the "Invalid username or password" error.  The username can be formatted as DOMAIN\username or username@DOMAIN.   Best, TJ ... View more

Hi Brad, Has the intersection functionality been added to suggest for geocoding services for locators built with your own data? Thanks. ... View more

Hey Tobias,   Seth Hiatt is correct,  the cause of the issue is related to the publishing database account not having the CREATE TABLE privilege.   The database user needs to have CREATE TABLE in order to create the SDE_UUID_TEMP$ table.  This table is required for replication in an Oracle geodatabase.  It is used to discover the lineage of a given object via its GlobalID value.  This is why you receive the error "No path for delta changes."   The table is created in the users' schema when synchronization is performed.  After the sync, the rows are deleted, but the table remains.  So you can revoke the CREATE TABLE privilege from the database user after running through the sync workflow one time. You don't have to do this for each service you publish, just once for the publishing user.  This issue does not occur when publishing as the data owner, because the data owner typically has CREATE TABLE.    http://desktop.arcgis.com/en/arcmap/10.6/manage-data/gdbs-in-oracle/replica-storage-oracle.htm "When a geodatabase is synchronized with its relative geodatabase, a table is created in the user's schema of the replica geodatabase (the one that is sending the changes to the relative geodatabase) to track the lineages of altered datasets.   The SDE_UUID_TEMP$ table is used to discover the lineage of a given object via its GlobalID value.   The SDE_UUID_TEMP$ table is not removed when the session exits because the table will likely be reused in another session."   To resolve this issue, grant CREATE TABLE to the publishing database user.  If you would like for that user to not have CREATE TABLE, revoke it after running the sync workflow successfully. ... View more