Hi Radhika,
Thanks for the question, the Alderstone CMT does indeed migrate from
non-unicode SQL Server to unicode SQL Server, with no issues. I agree with
other arslist posts, don't let the DB Migration convert to Unicode, there
are generally issues and you are of course right, 400Gb through the
>From your description, as long as nothing else but the Filter that calls the
>Run Process is executed on Submit then the record in your staging form should
>still be there.
This is the same methodology we use for all of our external interfaces.
- External system inserts record in
Radhika,
Yes it's expected behavior. Remedy is designed so that everything that
happens during an API call is a single transaction, and if that transaction
has an error, it rolls the entire thing back. If you don't want that you
have a few options. You can 'handle' the error and it won't roll
Hi,
I was under the impression that if a Phase 3 action on a submit filter met with
ARERR error, then the submitted record will still be present on the form , will
not get deleted or rolled back. However, I observed quite the contrary on ARS
8.1.02. Have you come across this before and how
Hi,
Is Alderstone CMT DB Migration solution also capable of migrating data from
non-unicode SQL Server to Unicode SQL Server ?
Previous arlist posts recommend not to carry out DB migration to convert
non-unicode to Unicode, instead install AR fresh with unicode and then use Java
API to
Hi Satya,Please could you provide detail for your below input:-"Click on More
Filters all the way to the right of the Search String. When we had this
issue we had fields saved in here which was causing the issue. This needs
to be fixed on each person's profile, if this is your issue."Early
6 matches
Mail list logo
