- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-13-2019 10:49 PM
Hi,
When you see [Unmodified customization] in the skip record, the message “There are no differences found” may appear. Why do skip records contain “There are no differences found” records?
best regards,
Solved! Go to Solution.
- Labels:
-
Multiple Versions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-13-2019 11:16 PM
Hello Tepp,
An upgrade will skip every record that was ever customized/changed. If you change any field it will be flagged "Customer updated" and will be skipped. The merging does not happen in a smart way, it just checks whether the record was flagged. So imagine that you have changed a string field from "foo" to "bar" and back to "foo". The value would be the same as OOTB, but the record has been updated, so will be skipped. Therefore, you should revert instead of just changing the value back.
The "skipped error" records in the upgrade history usually contains sys_properties data, that may already have been set in your instance. You can review the conflicting data to confirm the values and if the values are the same, you can leave the record as skipped. Most of these skipped error records also has a Priority of 5(low).
when you do a check on the skipped error records your will see that mostly the reason why this was the disposition of these updates is that it belong to a Scoped App Author or the Scoped App Client applications. Take note that these sys_properties are existing in your instance already.
Opening the Show Related Record link for these records results to the message below and no option to edit the record at all:
"This record is in the Scoped App Author application, but Global is the current application. To edit this record click here."
In comparison, open a record with Disposition "skipped" and you will have the options to Resolve Conflicts(comparison of Base system vs. Custom)or Revert to Base System.
Lastly, based on the Priority grade of these skipped error records should not have any effects on the behavior and functionality of your instance.
Please mark as Correct Answer/Helpful, if applicable.
Thanks!
Abhishek Gardade
Abhishek Gardade
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-13-2019 11:02 PM
Because even after applying them there won't be any changes to the script , if you have made. This
generally gives an indication to the user that these changes might not have been captured that is why
still the older version is coming in update set.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-13-2019 11:16 PM
Hello Tepp,
An upgrade will skip every record that was ever customized/changed. If you change any field it will be flagged "Customer updated" and will be skipped. The merging does not happen in a smart way, it just checks whether the record was flagged. So imagine that you have changed a string field from "foo" to "bar" and back to "foo". The value would be the same as OOTB, but the record has been updated, so will be skipped. Therefore, you should revert instead of just changing the value back.
The "skipped error" records in the upgrade history usually contains sys_properties data, that may already have been set in your instance. You can review the conflicting data to confirm the values and if the values are the same, you can leave the record as skipped. Most of these skipped error records also has a Priority of 5(low).
when you do a check on the skipped error records your will see that mostly the reason why this was the disposition of these updates is that it belong to a Scoped App Author or the Scoped App Client applications. Take note that these sys_properties are existing in your instance already.
Opening the Show Related Record link for these records results to the message below and no option to edit the record at all:
"This record is in the Scoped App Author application, but Global is the current application. To edit this record click here."
In comparison, open a record with Disposition "skipped" and you will have the options to Resolve Conflicts(comparison of Base system vs. Custom)or Revert to Base System.
Lastly, based on the Priority grade of these skipped error records should not have any effects on the behavior and functionality of your instance.
Please mark as Correct Answer/Helpful, if applicable.
Thanks!
Abhishek Gardade
Abhishek Gardade