Seed data for the Community automation suite (Technical, Online development @ web service APIs). The system user ticket we obtain through the PartnerSystemUserService seems to expire after about 20 minutes instead of the documented 8 hours. Is there a tenant setting that influences this?

Seed data for the Community automation suite (Technical, Online development @ web service APIs). A PATCH request to /api/v1/Contact/{id} with a UserDefinedFields entry returns 400 Bad Request, while the same change through PUT works. What is the correct JSON Patch path for user-defined fields?

user foru mmobile crm forum 

Content with symbols like & and &; and amp; or &

Test the & amp symbol and the &; symbol in content UI.

Auto Description alias animi quaerat

Auto Description quam corporis incidunt

desc Adding a question in technical to appear in latest 

It has come to our attention that the EventHandlers (Triggers) for Sales events (such as "After save sale") get a bit too much input data. Specifically, the EventData.inputValues contain also various local temporary variables which were never ment to be exposed. For instance, the value "SaleStageHasChanged", always has the value false  event though the stage actually has changed. This is because this is a private local variable, which should not be part of the EventData.inputValues. We will fix this bug down the road, but the fix will be to filter out (remove) these variables. Consequently, I ask you to not use them in your customizations as they are not stable and will be removed. Which ones are they? Unfortunately, I do not have a complete list for now. So, for simplicity, I believe you should limit your sulutions to using the standard values for properties on the entities, such as "SaleEntity.Amount", etc. The ID is definitely safe, and then you can query the database to get the current value. Sorry for this. We will try to clean up the inputValues, as well as getting some more documentation on this area.