0
Category:
STATUS DETAILS

Comments

Using GIT orders as source for X-docking scenarios would be very useful finctionality for lots of Companies. Please consider implementing the functionality.

Category:

It will be very useful if we can use financial tags in Management report. It will open new possibilities for solution across system and reduce the requirements of custom fields, and it can become source for many financial reports like cash flow, fund flow, auditing etc.Regards,CA Neeraj Kumar

Category:

Still waiting for this.

Category:

Error messages are definitely needed. The name of the constraint, attribute, calculation, or BOM lines that is causing the contradiction would shorten the debugging time significantly.Thank you

Category:

In the Event Planning Module, the current design allows the same Contact to register for an event multiple times.Can we have a feature that only allows each Contact to register once for each event?This makes sense, as registering the same person twice does not have any meaning. In the registration form, if we detect that the same Contact has already registered, it should return a warning or message on the front end to notify the user that they have already registered for this event.

Category:

When registering for an event with the same name and email it created multiple registrations - it would be good if these were automatically merged ti prevent capacity being reached for events when actually there was space available

Category:

It would be great if the system can detect the duplicate registration for the event and prohibit that.
It seems like the system understands it as session registration and it is not and when we are sending the reminder to join it includes e.g. two CTA for joining for the same event.

Category:

The event registration process does not consider multiple submissions as duplicates because the platform allows a single contact to have multiple registrations for the same event. This design supports scenarios where attendees may register for different sessions or ticket types under the same event.To address your concern about preventing duplicate registrations for the same contact within the same event, the feature that should be implemented is a duplicate check at the Event Registration level. This enhancement would:Validate whether an existing registration already exists for the same contact and event combination.Block or prompt the user before creating a new registration for the same event.Provide flexibility to configure exceptions (e.g., allow multiple registrations for multi-session events if required).This functionality is not currently available out-of-the-box, as matching rules apply only to Contacts and not to Event Registrations. Implementing this feature would require either:A custom plugin for synchronous validation during registration, orA Power Automate flow with logic to check existing registrations before creating a new one.

Category:

This would be HUGE especially with how fast Copilot adoption is happening.

Category:

@beatriz This feature was deprecated after being released. Are there any plans to reintroduce this or a similar feature in future releases?

Category:

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 500