Comments
I agree that this functionality doesn't make sense in its current format. I can't imagine a scenario where you'd ever need a second authorisation if only thing on the journal that has changed, is 'Exported to Payment File' going from from false to true. Fixing this would be of great benefit to many users I'm sure!
We can’t use “Any to Organization “in an entity that is person as the verification for the party, any in this case can be used for person or organization and the other part will be used for organization which is conflicting with the logic of the relation to include the entity that you create the relation on in one of the party of the organizationAnd it goes the other way around if you are trying to use a relation that is “Any to Person “within organization entity you will face the same conflict.This is for verification as the entity type that you will create the relation for needs to be included in the relation type that you will be using.To avoid that you would need to use “Any to Any” in the relation and only then you will be able to use the same relation ID in both organization and person types. A change in the logic needs to be in place for Any to Organization to occupy person and vice versa.
I assume but would be nice to get a comment on the roadmap for details and also contacts... Is my request in the roadmap or is there a way to grab this data via powerbi and report. Same question about getting contract reports since as of today only leads are shown in sales acceleration reporting? Thanks
My CV is Resrved for Las Vegas Ignite Microsoft biggest meeting and my business role for our future plan. I am create plan with more than two year step by step experience, today I can say loud. I am so close to open my agency insade Microsoft wholesale and be direct Gold provider for Distribution devices and mobiles phones with direct cooperation with Android enterprise and migrations insade Intuitive Azure and my Microsoft account.