Skip to main content
Liquid error: Exception has been thrown by the target of an invocation.

Vote (0) Share
's profile image

on

Comments (Liquid error: Exception has been thrown by the target of an invocation.)
's profile image Profile Picture

Mikkel Hansen on 27 Jun 2024 11:30:24

RE:

Hi @Emma husbergDo you have any news from Microsoft on this one?We are currently setting the approval flow up wth a customer and they want to have inventory adjustment journals with a amount value above a certain amount to be reviewed by Finance after the Warehouse manager has approved it. So having the amount field as an option in the workflow would solve that

's profile image Profile Picture

Peter van Bergen on 27 Jun 2024 09:44:03

RE:

Also still waiting for the simple (+) function. Adding more filter criteria in advanced filtering should already be available, but unfortunately it is not.

's profile image Profile Picture

Erwin de Kreuk on 27 Jun 2024 08:48:05

RE:

+100. Hopefully this will arrive soon in West Europe, we really need to have this

's profile image Profile Picture

Telmo GABRIEL VIEIRA on 27 Jun 2024 07:30:17

RE:

This is a must have ! Many international paiements need to be processed through and intermediary bank account.

's profile image Profile Picture

Christine Maria Ødegård on 27 Jun 2024 06:33:36

RE:

Cloning content blocks as well.

's profile image Profile Picture

on 27 Jun 2024 05:45:44

RE:

Interested in How A.I. Can Transform Your Business?

Click the link below to find out!

https://bit.ly/4c8cnmJ

's profile image Profile Picture

Simon Roh on 27 Jun 2024 04:27:51

RE:

Quite surprising such a simple feature has been missed when transitioned to RTM. Please bring back the ability to export segment members.

's profile image Profile Picture

Martha Chronister on 26 Jun 2024 23:37:18

RE:

This would greatly help me as I post multiple trade agreements daily, and this would make my job faster and catch errors before posting.

's profile image Profile Picture

J N on 26 Jun 2024 16:45:08

RE:

100% agree. Sometimes terminology changes and it needs to be reflected in the semantic layer. This basically makes it extremely difficult when trying to promote shared semantic models that have dozens of thin reports connected...or any other downstream use of a semantic model Microsoft leverages.Running into this issue now with a dataflow column name change that feeds multiple shared semantic models, and essentially dozens and dozens of reports that need to be modified in the Service; as well as awareness to anyone using those semantic models outside of the Service.

's profile image Profile Picture

Jean-Paul Nicophene on 26 Jun 2024 15:25:20

RE:

This has been planned since 2021, and we're currently in 2024. Are there any updates on this?