on
RE:
Hi there, thank you for your feedback, It's much appreciated. I think that this may satisfy the requirement. A further example of the use case is below. Please let me know your thoughts, thank you. Also, can you please advise of the expected date that this new feature will go live? Many thanks!Example of a Journey (1 Year duration) 'Journey A' has an invoking segment including the field and value 'marketing consent = yes'John Appleseed has a this field set to 'yes' (Contact or Lead record) and therefore enters 'Journey A' 90 days later, John Appleseed changes his marketing preference to 'no' (Contact or Lead record) via a website which updates his marketing preference on his record via power automate.The change is registered by and exclusion segment or trigger, which includes 'marketing consent = no', within 'Journey A'John Appleseed is removed from 'Journey A'10 days later, John Appleseed changes his marketing preference to 'yes' (Contact or Lead record) via a conversation with a Sales rep who updates his marketing preference on his record to 'yes'John Appleseed is entered into 'Journey A' once again.If the 'Email Duplication' feature switch toggle is set to 'on' and if John Appleseed has not changed his email address, he should not receive duplicates of email he has previously received from 'Journey A'
RE:
As we have in org. management active positions and all positions it would be really useful to have the same lists for the jobs. In the job list, there is a button - manage changes, where we have a possibility to set an expiration date. However, expired jobs are still visible in the list and also they come up when we link a position with the job. So what is the purpose of having an expiration date in jobs?
Since the organizational needs are evolving, from time to time we add new jobs and eliminate old ones. Currently, the only way to hide expired jobs is to delete them from the list which also requires deleting the history from position details. I believe it is not the correct way to manage historical data.
My suggestion is to have two lists: active jobs and all jobs (where we will find expired jobs as well). So when the user will assign the job to the position an active list will be showing up.
Furthermore, if the inactive job is still needed then from manage changes a new time period will be set which will make a job active again.
I am sure this feature will enrich the job management process and make it easier to maintain jobs' data. Besides this feature will enable to keep the historical data in the position details.
RE:
This is actually a very needed functionality.
RE:
Please vote this idea - because of that MS spoiled standard Foreign currency revaluation in GL (you cannot reverse revaluation in a new year after closing previous year. Why? Because they introduced a fix, not for Poland, but for Italy and that fix now is refusing reversing foreign revaluation in a new year)
RE:
I was in process of raising exactly the same idea!
RE:
This is very much needed for my organization! Can something be done to allow scrolling in a tooltip?
RE:
Yes, we definitely need a PA activity! For example to build in an approval step for validating master data inside a pipeline.
RE:
For batch-based industries using batch attributes actively, specifically for customer specific attributes, inheriting all the batch information between companies is critical.
RE:
Thomas, keep in mind sorting on the fields depends on the key chosen by the system (not necessarly) the one selected by the programmer. This can affect your sorting order and yield wrong min/max