Enhancement of Misc/Set-BcContainerFeatureKeys.ps1 to be able to Enable Feature key for particular company. #3696
Conversation
Mea Culpa - Despite the fact I confirmed it works correctly, I provided wrong code from incorrect branch in my repository, sorry for that. Never will happen again.
Added update of table [dbo].[Feature Data Update Status$63ca2fa4-4f03-4f2b-a480-172fef340d3f] as this table has to be updated as well to "mark" feature as activated/deactivated.
Optionally is possible to activate Feature for particular company. No data update is initiated there (main reason is to enable Feature for automated tests)
|
@microsoft-github-policy-service agree
From: microsoft-github-policy-service[bot] ***@***.***>
Sent: Wednesday, October 2, 2024 2:45 PM
To: microsoft/navcontainerhelper ***@***.***>
Cc: Adamec, Jiri ***@***.***>; Mention ***@***.***>
Subject: Re: [microsoft/navcontainerhelper] Enhancement of Misc/Set-BcContainerFeatureKeys.ps1 to be able to Enable Feature key for particular company. (PR #3696)
[EXTERNAL E-MAIL] Use caution when following links or opening attachments.
@KM-JAD<https://github.com/KM-JAD> please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@microsoft-github-policy-service agree [company="{your company}"]
Options:
* (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
@microsoft-github-policy-service agree
* (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.
@microsoft-github-policy-service agree company="Microsoft"
Contributor License Agreement
Contribution License Agreement
This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your
contributions to Microsoft open source projects. This Agreement is effective as of the latest signature
date below.
1. Definitions.
“Code” means the computer software code, whether in human-readable or machine-executable form,
that is delivered by You to Microsoft under this Agreement.
“Project” means any of the projects owned or managed by Microsoft and offered under a license
approved by the Open Source Initiative (www.opensource.org<http://www.opensource.org>).
“Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
Project, including but not limited to communication on electronic mailing lists, source code control
systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
discussing and improving that Project, but excluding communication that is conspicuously marked or
otherwise designated in writing by You as “Not a Submission.”
“Submission” means the Code and any other copyrightable material Submitted by You, including any
associated comments and documentation.
2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any
Project. This Agreement covers any and all Submissions that You, now or in the future (except as
described in Section 4 below), Submit to any Project.
3. Originality of Work. You represent that each of Your Submissions is entirely Your original work.
Should You wish to Submit materials that are not Your original work, You may Submit them separately
to the Project if You (a) retain all copyright and license information that was in the materials as You
received them, (b) in the description accompanying Your Submission, include the phrase “Submission
containing materials of a third party:” followed by the names of the third party and any licenses or other
restrictions of which You are aware, and (c) follow any other instructions in the Project’s written
guidelines concerning Submissions.
4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else
for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
Submission is made in the course of Your work for an employer or Your employer has intellectual
property rights in Your Submission by contract or applicable law, You must secure permission from Your
employer to make the Submission before signing this Agreement. In that case, the term “You” in this
Agreement will refer to You and the employer collectively. If You change employers in the future and
desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
and secure permission from the new employer before Submitting those Submissions.
5. Licenses.
* Copyright License. You grant Microsoft, and those who receive the Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
parties.
* Patent License. You grant Microsoft, and those who receive the Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
Your patent claims that are necessarily infringed by the Submission or the combination of the
Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
import or otherwise dispose of the Submission alone or with the Project.
* Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
granted by implication, exhaustion, estoppel or otherwise.
1. Representations and Warranties. You represent that You are legally entitled to grant the above
licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
have disclosed under Section 3). You represent that You have secured permission from Your employer to
make the Submission in cases where Your Submission is made in the course of Your work for Your
employer or Your employer has intellectual property rights in Your Submission by contract or applicable
law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
2. Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
You later become aware that would make Your representations in this Agreement inaccurate in any
respect.
3. Information about Submissions. You agree that contributions to Projects and information about
contributions may be maintained indefinitely and disclosed publicly, including Your name and other
information that You submit with Your Submission.
4. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
defenses of lack of personal jurisdiction and forum non-conveniens.
5. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
supersedes any and all prior agreements, understandings or communications, written or oral, between
the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.
—
Reply to this email directly, view it on GitHub<#3696 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ATNC73IJLADY4RGB7BZHAU3ZZPTE7AVCNFSM6AAAAABPHTDIG6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBYGU2TMOBUGQ>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
|
Please also add a line to the upper section of the release notes |
Rebuilt code to be easy to understand it
|
I added another write-host - but I think there is still something wrong here... With the change in this PR - we only ever change anything if the feature exists in the table Feature Data Update Status`$63ca2fa4-4f03-4f2b-a480-172fef340d3f. [bcserver]: PS C:\Run> Invoke-Sqlcmd -Database 'default' -Query "SELECT ""Feature Key"" FROM [dbo].[Feature Data Update Status`$63ca2fa4-4f03-4f2b-a480-172fef340d3f]" Feature KeySalesPrices None of these are in the tenant Feature key table. |
|
The reason for these dumps is really to see where things goes wrong if they go wrong - see which SQL statement causes the error - that is the reason. But... - with your change - the only values that can be used with this function are these: SalesPrices as that is the content of the data update table. I cannot call this with any other key - I don't assume that that is the way it should be? I would like to understand how this function is supposed to work - after all - I am the one needing to support this going forward. Currently - the creation of a new record in Tenant Feature Key also doesn't work - as the SQL Query contains [CRONUS] database name as well - and that fails always - so the [CRONUS] part needs to go away I guess. I will try to describe how I think this function should work (after fixing the CRONUS item above).
Is that the intended functionality? |
Yes, those four records are in database by default for company Cronus international, but you can create them also using configuration packages (instead of auto creation during opennig of page 2610)
well, yes, [CRONUS] is there the same way, as there is Business Central instance "BC' :) . Works now perfectly for containers, but I think it will work w/o that as well.
yes, it is :) Please note that standard BC database downloaded from MS repository has a bit inconsistent data records in both our tables. |
You specify -databaseName $databaseName and [CRONUS] - that doesn't work. |
you are correct -> already fixed |
removed database name [CRONUS] from invoked SQL command on line 100.
New function for SaaS BC environment restart.
New function Restart-BcEnvironment added for SaaS BC environment restart.
New function to obtain SaaS BC sessions.
New function to stop and delete SaaS BC session.
Two new functions to obtain sessions and to delete session in SaaS BC .
Two new functions to obtain sessions and to delete session in SaaS BC.
|
Hi Freddy, is there anything missing from my side? |
(There is no activated any data upgrade. This must be initiated manually as usual, if it is really needed).
Fixes #3609